CVE-2026-86818
Last modified
CVE-2026-86818 is a medium-severity vulnerability rated 4.8/10 on the CVSS scale. 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| fast-uri | fast-uri | >= 4.1.3, < 4.1.5 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-86818?
How severe is CVE-2026-86818?
How do I fix CVE-2026-86818?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-8681The Essential Chat Support plugin for WordPress is vulnerabl…5.3
- CVE-2026-86810A vulnerability was detected in Open-Web-Analytics up to 1.9…7.3
- CVE-2026-86812The WPCafe WordPress plugin before 3.0.18 does not correctl…6.5
- CVE-2026-86813The MetForm WordPress plugin before 4.1.9 does not properly …4.8
- CVE-2026-86814The UsersWP WordPress plugin before 1.5.10 does not verify …8.1
- CVE-2026-86815The BackWPup WordPress plugin before 5.7.5 does not properl…5.5
- CVE-2026-86819Waves Central for macOS contains a local privilege escalatio…7.1
- CVE-2026-8682The 3D Viewer – 3D Model Viewer – Augmented Reality – Virtua…4.3
- CVE-2026-86823The Newsletter WordPress plugin before 9.3.7 does not valid…5.3
- CVE-2026-86824The Newsletter WordPress plugin before 9.3.8 does not gener…4.8
- CVE-2026-8683Mattermost Desktop App versions <=6.1 5.5.13.0 fail to accou…6.5
- CVE-2026-86830Incorrect privilege assignment in Temporary Elevated Access …7.2
Are you affected by CVE-2026-86818?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
