GitHub Advisoryadvisory · npm

GHSA-rx4f-c7p8-82vq undici vulnerable to Denial of Service via WebSocketStream unclean close

MEDIUM Published 2026-09-29 Modified 2026-09-29 Official page ↗
Aliases
CVE-2026-85014
Ecosystem
npm
Packages
undici
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses
CWE-248, CWE-754
Reviewed
2026-09-29

Affected packages

• npm undici: >= 7.0.0, < 7.29.1 → fixed in 7.29.1 • npm undici: >= 8.0.0, < 8.10.2 → fixed in 8.10.2

Description

Impact undici's `WebSocketStream` crashes the client process when a WebSocket connection is closed abruptly without a close handshake. On such an unclean close, the internal socket-close handler calls `abort()` on the writable stream even when the application holds a writer lock. Per the WHATWG Streams standard, aborting a locked stream returns a promise that rejects with a `TypeError`, and the handler discards that promise. The unobserved rejection surfaces as an `unhandledRejection` and, under Node.js's default behavior, terminates the process. A malicious or compromised WebSocket server can crash a client with a single connection teardown (a TCP reset, a proxy teardown, or a protocol-violating frame). Affected applications are those using the `WebSocketStream` API and writing through a writer, which is the standard way to write. All releases from undici 7.0.0 are affected. WebSocketStream was introduced in 7.0.0. Patches Upgrade to undici v7.29.1 or v8.10.2. Workarounds No workaround is available.

Related

Alias · CVE (1)

  • CVE-2026-85014 undici's experimental WebSocketStream client crashes the whole Node.js process when a remote peer closes the TCP connection without a… vulnerability

Weakness · CWE (2)

  • CWE-248 Uncaught Exception weakness
  • CWE-754 Improper Check for Unusual or Exceptional Conditions weakness

References