CVE-2026-86818
- Source
- https://cve.org/CVERecord?id=CVE-2026-86818
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-86818.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-86818
- Aliases
-
- GHSA-jvvf-x445-j334
- Downstream
- Published
- 2026-09-15T10:40:38Z
- Modified
- 2026-09-17T03:30:55Z
- Severity
-
- 4.8 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N CVSS Calculator
- Summary
- fast-uri vulnerable to mailto header injection via percent-encoded field-name desynchronization
- Details
-
fast-uri is a dependency-free RFC 3986 URI parser for Node.js, used by Fastify and ajv, that added a mailto scheme parser in version 4.1.3. In versions 4.1.3 and 4.1.4, the mailto parser compares each query field name to the reserved names to, subject, and body while the name is still percent-encoded, and decodes it only when storing it as a generic header, so a percent-encoded spelling of a reserved field name is not recognized as that field at parse time but is re-emitted as the literal field name when the parsed URI is serialized. An application that validates, logs, or displays the recipient list from the first parse and then serializes the URI and sends it can silently gain an attacker-chosen recipient, and the subject and body fields can be smuggled across the same roundtrip. The issue is fixed in fast-uri 4.1.5, and users should upgrade to 4.1.5 or later. As a workaround, do not act on a mailto URI that fast-uri has re-serialized without first decoding and re-validating its recipient, subject, and body fields.
- Database specific
{ "cna_assigner": "openjs", "cwe_ids": [ "CWE-172", "CWE-436" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/86xxx/CVE-2026-86818.json" }- References