CVE-2026-85014: undici vulnerable to Denial of Service via WebSocketStream unclean close

Published Sep 4, 2026
·
Updated

undici's experimental WebSocketStream client crashes the whole Node.js process when a remote peer closes the TCP connection without a WebSocket close handshake. On an unclean close the internal socket-close handler calls abort on the writable stream unconditionally and discards the returned promise, but per the WHATWG Streams standard aborting a locked writable returns a promise that rejects with a TypeError. Because the application holds a writer on that writable, which is the only way to write, the rejection is never observed and Node's default unhandled-rejection behavior terminates the process. An untrusted server can therefore crash a client with a single abrupt disconnect, with no authentication and no application mistake. This affects undici versions from 7.0.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.

Affected Software

2 affected components
npm/undici>=7.0.0<=7.29.1
npm/undici>=8.0.0<=8.10.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade undici to a version that resolves this vulnerability.

    Fixed in 7.29.1
  2. Upgrade

    Upgrade undici to a version that resolves this vulnerability.

    Fixed in 8.10.2

Event History

Sep 4, 2026
CVE Published
via MITRE·04:30 PM
Data Sourced
via MITRE·04:30 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which applications are exposed to this denial of service?

Applications using undici's experimental WebSocketStream client are exposed when they connect to an untrusted or attacker-controlled server. The affected ranges are stated as undici 7.0.0 through 7.29.1 and 8.0.0 through 8.10.2.

2

What does an attacker need to do to trigger the crash?

The attacker only needs to operate or control a remote peer that can abruptly close the TCP connection without completing a WebSocket close handshake. No authentication or application mistake is required.

3

How can I determine whether my application is affected?

Check whether the application uses the experimental WebSocketStream client and inventory its installed undici version. The crash condition applies when the application holds a writer on the writable stream, which is required in order to write.

4

What remediation does the advisory recommend?

The advisory recommends upgrading undici to version 7.29.1 or 8.10.2.

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