ubuntu-cve-2026-15157
Vulnerability from osv_ubuntu
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": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-llhttp",
"binary_version": "9.1.3~5.26.3+dfsg1+~cs23.10.12-2"
},
{
"binary_name": "node-undici",
"binary_version": "5.26.3+dfsg1+~cs23.10.12-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "node-undici",
"purl": "pkg:deb/ubuntu/node-undici@5.26.3+dfsg1+~cs23.10.12-2?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.22.1+dfsg1+~cs20.10.10.2-1ubuntu1",
"5.26.3+dfsg1+~cs23.10.12-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "node-undici",
"binary_version": "7.18.2+dfsg+~cs3.2.0-1build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "node-undici",
"purl": "pkg:deb/ubuntu/node-undici@7.18.2+dfsg+~cs3.2.0-1build1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"7.3.0+dfsg1+~cs24.12.11-2",
"7.16.0+dfsg+~cs3.2.0-2",
"7.18.2+dfsg+~cs3.2.0-1",
"7.18.2+dfsg+~cs3.2.0-1build1"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2026-15157",
"modified": "2026-07-31T00:00:00Z",
"published": "2026-07-31T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-15157"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15157"
},
{
"type": "REPORT",
"url": "https://github.com/nodejs/undici/security/advisories/GHSA-m8rv-5g2x-5cg5"
},
{
"type": "REPORT",
"url": "https://cna.openjsf.org/security-advisories.html"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-15157"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.