CVE-2026-109869: undici vulnerable to Denial of Service via unhandled error on excessive content-encodings
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
undicito a version that resolves this vulnerability.Fixed in 6.29.1 - Upgrade
Upgrade
undicito a version that resolves this vulnerability.Fixed in 7.30.1 - Upgrade
Upgrade
undicito a version that resolves this vulnerability.Fixed in 8.12.2
Event History
Frequently Asked Questions
Which applications are exposed to this denial of service?
Applications using undici's fetch() implementation in versions 6.23.0 through 6.29.0, 7.18.0 through 7.30.0, or 8.0.0 through 8.12.1 are affected. Exposure requires the application to fetch from a server that an attacker can control or maliciously influence.
What does an attacker need to do to trigger the crash?
A remote unauthenticated server need only return a response with more than five Content-Encoding values and close the connection before sending the body. A single such response can terminate the Node.js process.
Does catching fetch() errors prevent exploitation?
No. The process can still crash even when the application correctly catches the fetch() rejection, because an orphaned internal response stream later emits an unhandled error.
What should teams do if they cannot upgrade immediately?
There is no workaround. Upgrade undici to 6.29.1, 7.30.1, 8.12.2, or a later version.