{"id":"GHSA-jvvf-x445-j334","revision":"4f1d6142ba7f418ba4f9f63f19c3e8fa","records":[{"revision":"4f1d6142ba7f418ba4f9f63f19c3e8fa","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-jvvf-x445-j334","aliases":["CVE-2026-86818"],"title":"fast-uri vulnerable to mailto header injection via percent-encoded field-name desynchronization","description":"### Impact\n\n`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`.\n\nAn 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.\n\n### Patches\n\nUpgrade to `fast-uri` 4.1.5.\n\n### Workarounds\n\nPercent-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.","state":0,"publishedAt":"2026-09-29T23:51:16+00:00","modifiedAt":"2026-09-30T00:00:03.8545188+00:00","affected":[{"ecosystem":"npm","name":"fast-uri","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"4.1.3"},{"kind":"fixed","version":"4.1.5"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"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","https://github.com/fastify/fast-uri/releases/tag/v4.1.5"],"sourceUrl":"https://github.com/advisories/GHSA-jvvf-x445-j334","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-jvvf-x445-j334","identifiers":["GHSA-jvvf-x445-j334","CVE-2026-86818"]},"retained":false,"historicalAffected":[]}],"coverage":[]}