CVE-2026-15157

published 29 Jul 2026 · updated 16 Nov 2026

undici vulnerable to CRLF Injection via blob-like body 'type' property

4.2MediumCVSS 4.2EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 6.28.0, 7.29.0 and 8.9.0.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
undici<6.28.0, >=7.0.0 <7.29.0, >=8.0.0 <8.9.06.28.0, 7.29.0, 8.9.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-15157 severity on Zeptric[![CVE-2026-15157](https://zeptric.io/badge/cve/CVE-2026-15157.svg)](https://zeptric.io/cve/CVE-2026-15157)