UBUNTU-CVE-2026-109869 (CVE-2026-109869)
Vulnerability from osv_ubuntu – Published: 2026-10-15 19:17 – Updated: 2026-10-28 17:50 – Source websiteundici is an HTTP client library for Node.js. In versions 6.23.0 through 6.29.0, 7.18.0 through 7.30.0, and 8.0.0 through 8.12.1, its fetch() implementation crashes the Node.js process when a malicious server returns a response with more than five content codings and closes the connection before sending the body. undici rejects such responses because of a content-encoding limit, but it created the internal response stream before that check and returned without attaching an error listener or aborting the request, so the early close surfaces a content-length mismatch on the orphaned stream, which Node.js treats as an unhandled error and terminates the process. A remote, unauthenticated server can trigger this with a single response, even when the application correctly catches the fetch() rejection, resulting in a denial of service. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, and users should upgrade to one of those versions or later. There is no workaround.
{
"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": "8.9.0+dfsg+~cs3.2.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "node-undici",
"purl": "pkg:deb/ubuntu/node-undici@8.9.0+dfsg+~cs3.2.0-1?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"7.18.2+dfsg+~cs3.2.0-1build1",
"7.24.6+dfsg+~cs3.2.0-3",
"8.5.0+dfsg+~cs3.2.0-2",
"8.5.0+dfsg+~cs3.2.0-3",
"8.9.0+dfsg+~cs3.2.0-1"
]
},
{
"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 is an HTTP client library for Node.js. In versions 6.23.0 through 6.29.0, 7.18.0 through 7.30.0, and 8.0.0 through 8.12.1, its fetch() implementation crashes the Node.js process when a malicious server returns a response with more than five content codings and closes the connection before sending the body. undici rejects such responses because of a content-encoding limit, but it created the internal response stream before that check and returned without attaching an error listener or aborting the request, so the early close surfaces a content-length mismatch on the orphaned stream, which Node.js treats as an unhandled error and terminates the process. A remote, unauthenticated server can trigger this with a single response, even when the application correctly catches the fetch() rejection, resulting in a denial of service. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, and users should upgrade to one of those versions or later. There is no workaround.",
"id": "UBUNTU-CVE-2026-109869",
"modified": "2026-10-28T17:50:33Z",
"published": "2026-10-15T19:17:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-109869"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-109869"
},
{
"type": "REPORT",
"url": "https://github.com/nodejs/undici/security/advisories/GHSA-xjj6-f33q-929c"
},
{
"type": "REPORT",
"url": "https://cna.openjsf.org/security-advisories.html"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-109869"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.