CVE-2026-109869: undici vulnerable to Denial of Service via unhandled error on excessive content-encodings

Published Oct 15, 2026
·
Updated

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

1 affected component
npm/undici>=6.23.0<=6.29.0, >=7.18.0<=7.30.0, >=8.0.0<=8.12.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade undici to a version that resolves this vulnerability.

    Fixed in 6.29.1
  2. Upgrade

    Upgrade undici to a version that resolves this vulnerability.

    Fixed in 7.30.1
  3. Upgrade

    Upgrade undici to a version that resolves this vulnerability.

    Fixed in 8.12.2

Event History

Oct 15, 2026
CVE Published
via MITRE·06:08 PM
Data Sourced
via MITRE·06:08 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203