CVE-2026-86818: fast-uri vulnerable to mailto header injection via percent-encoded field-name desynchronization
Impact fast-uri's mailto scheme parser compares each query field name to the reserved names (to, subject, body) while the name is still percent-encoded, and only percent-decodes it when storing it as a generic header.
Published Sep 29, 2026
Affected packages
fast-uri
- Ecosystem
- npm
- Affected
- >= 4.1.3, < 4.1.5
- Fixed in
- 4.1.5
- Check
npm ls fast-uri
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
fast-uri's mailto scheme parser compares each query field name to the reserved names (to, subject, body) while the name is still percent-encoded, and only percent-decodes it when storing it as a generic header. On serialize, the decoded name is re-emitted, so a field name such as %74o (percent-encoded to) is not recognized as a recipient at parse time (parse().to shows only the legitimate recipient) but materializes as a literal to= field after serialize(), and reparsing then treats it as a recipient. The same technique smuggles subject and body through %73ubject and %62ody.
An application that parses an untrusted mailto URI, makes a display, allowlist, or logging decision on parse().to, then re-serializes the result and passes the serialized string to a mail client or an outbound send path can gain an attacker-chosen recipient, subject, or body that was not visible when the recipient list was checked. A scanner inspecting the raw input for an extra to= sees nothing, because the injected field appears only after fast-uri serializes.
Patches
Upgrade to fast-uri 4.1.5.
Workarounds
Percent-decode and compare mailto field names case-insensitively before trusting parse().to, or re-check the recipient list on the serialized output rather than only on the initial parse, until upgrading.
Credited to manus-use, mcollina, UlisesGascon, manus-pi.
References
- https://github.com/fastify/fast-uri/security/advisories/GHSA-jvvf-x445-j334
- https://nvd.nist.gov/vuln/detail/CVE-2026-86818
- https://github.com/fastify/fast-uri/commit/f40a88f33e684a46faec3f5b820bcbb1e85add64
- https://cna.openjsf.org/security-advisories.html
- https://github.com/fastify/fast-uri/releases/tag/v4.1.5
- https://github.com/advisories/GHSA-jvvf-x445-j334
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-110095
fast-uri vulnerable to improper path equivalence in relative reference normalization
low3.7Oct 23, 2026CVE-2026-110180
fast-uri vulnerable to host confusion via unchecked WHATWG host canonicalization
medium4.8Oct 23, 2026CVE-2026-110306
fast-uri vulnerable to URI scheme spoofing via percent-encoded scheme decoding
medium6.1Oct 23, 2026CVE-2026-110725
fast-uri vulnerable to scheme injection via an unescaped first-segment colon in suffix references
low3.7Oct 23, 2026CVE-2026-86472
fast-uri vulnerable to inconsistent host case normalization via percent-encoded octets
medium4.8Sep 29, 2026CVE-2026-84292
fast-uri vulnerable to authority injection via an unvalidated port in serialize
high7.5Sep 28, 2026
