CVE-2026-15157
Last modified
CVE-2026-15157 is a medium-severity vulnerability rated 5.4/10 on the CVSS scale. undici does not validate the type property of a duck-typed blob-like request body before using it as the Content-Type header on the HTTP/1.1 dispatcher. In undici before 6.28.0, from 7.0.0 up to before 7.29.0, and from 8.0.0 up to before 8.9.0, an application that passes a hand-rolled blob-like body (via request, stream, pipeline, or dispatch) whose type is derived from untrusted input allows an attacker to inject CRLF sequences and append arbitrary HTTP headers, potentially smuggling a second request past the upstream. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
undici does not validate the type property of a duck-typed blob-like request body before using it as the Content-Type header on the HTTP/1.1 dispatcher. In undici before 6.28.0, from 7.0.0 up to before 7.29.0, and from 8.0.0 up to before 8.9.0, an application that passes a hand-rolled blob-like body (via request, stream, pipeline, or dispatch) whose type is derived from untrusted input allows an attacker to inject CRLF sequences and append arbitrary HTTP headers, potentially smuggling a second request past the upstream. Native Blob objects are safe because their constructor strips CRLF from the type, and fetch is unaffected because it validates headers, but ecosystem libraries that build duck-typed blob shapes from user input can reach the vulnerable path. This is the same defect class as CVE-2022-35948 and CVE-2026-1527, on a header sink that the earlier fixes did not cover. The issue is fixed in undici 6.28.0, 7.29.0, and 8.9.0.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Nodejs | Undici | < 6.28.0 |
| Nodejs | Undici | >= 7.0.0, < 7.29.0 |
| Nodejs | Undici | >= 8.0.0, < 8.9.0 |
References
- https://cna.openjsf.org/security-advisories.htmlVendor Advisory
- https://github.com/nodejs/undici/security/advisories/GHSA-m8rv-5g2x-5cg5Mitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-15157?
How severe is CVE-2026-15157?
How do I fix CVE-2026-15157?
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-15151The Five Star Restaurant Reservations WordPress plugin befo…7.5
- CVE-2026-15152The WP Hotel Booking WordPress plugin before 2.3.2 does not …5.3
- CVE-2026-15153The WP Hotel Booking WordPress plugin before 2.3.2 does not …6.8
- CVE-2026-15154A flaw was found in `guardrails-detectors`, a component of R…6.5
- CVE-2026-15155The Essential Addons for Elementor – Popular Elementor Templ…8.8
- CVE-2026-15156The Essential Addons for Elementor – Popular Elementor Templ…6.4
- CVE-2026-15158The Blocksy Companion plugin for WordPress is vulnerable to …9.8
- CVE-2026-15159The Ninja Forms - Excel Export plugin for WordPress is vulne…4.3
- CVE-2026-1516GitLab has remediated an issue in GitLab EE affecting all ve…5.7
- CVE-2026-15160The Ninja Forms - Excel Export plugin for WordPress is vulne…4.3
- CVE-2026-15161The Ninja Forms - Excel Export plugin for WordPress is vulne…6.4
- CVE-2026-15163Multiple protocol dissector infinite loops in Wireshark 4.6.…7.5
Are you affected by CVE-2026-15157?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
