CVE-2026-109932: undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering
A malicious or compromised WebSocket server can crash a Node.js process that uses undici's WebSocket client, including the built-in `globalThis.WebSocket`. It streams small PING frames and never reads the PONG replies, so memory grows until the process dies. Upgrade undici to 6.29.1, 7.30.1 or 8.12.2. There is no workaround.
Published Oct 27, 2026 · Analysis Nov 1, 2026
What an attacker can do
For every PING frame it receives, the undici WebSocket receiver writes a PONG back to the socket. It ignores the false return value of socket.write(), which is the backpressure signal. A server that sends many small PINGs and never reads the client's PONGs makes the outbound write queue, and the heap, grow without limit. The Node.js process eventually runs out of memory and exits.
The attack is asymmetric: small inbound frames produce a much larger retained queue. The attacker needs only to be the server end of a normal WebSocket connection, with no authentication. In practice this means any client of yours that connects to a server you do not fully control, or to one that has been compromised: a bot, a crawler, a browser-like worker, a CLI or a backend that dials third-party WebSocket endpoints. Availability is the only impact. CVSS rates attack complexity high because the victim must connect to the hostile server first.
Node.js bundles undici, so code using the global WebSocket without installing undici is exposed through the runtime version.
Who is affected
undici from 5.15.0 (where the WebSocket client appeared) up to before 6.29.1, 7.0.0 up to before 7.30.1, and 8.0.0 up to before 8.12.2. Servers that only accept WebSocket connections through other libraries are not in scope; the flaw is in the client.
Check your dependency tree:
npm ls undiciIf you rely on globalThis.WebSocket, also check node --version, because the bundled copy depends on the Node.js release. The sources do not list which Node.js releases carry the fix.
undici
- Ecosystem
- npm
- Affected
- >= 5.15.0, < 6.29.1
- Fixed in
- 6.29.1
- Check
npm ls undici
undici
- Ecosystem
- npm
- Affected
- >= 7.0.0, < 7.30.1
- Fixed in
- 7.30.1
- Check
npm ls undici
undici
- Ecosystem
- npm
- Affected
- >= 8.0.0, < 8.12.2
- Fixed in
- 8.12.2
- Check
npm ls undici
How to fix it
Upgrade to 6.29.1, 7.30.1 or 8.12.2, whichever matches your major version.
npm install [email protected]The patch pauses WebSocket frame parsing when the automatic PONG hits socket backpressure and resumes it when the socket drains, which bounds the outbound queue. The advisory lists no workarounds. Where you cannot upgrade, limit which WebSocket servers your code can connect to.
How to tell if you were hit
Look for Node.js processes whose resident memory climbs steadily while holding one open WebSocket connection, followed by an out-of-memory exit such as JavaScript heap out of memory or a kernel OOM kill. In packet captures or proxy logs, the signature is a peer that sends a steady stream of small ping frames and never reads or acknowledges the data you send. Identify which outbound WebSocket URL the crashed process was connected to.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Impact
undici's WebSocket client (including Node.js's bundled globalThis.WebSocket) can be driven to exhaust process memory by a malicious or compromised WebSocket server. For every PING frame received, the receiver automatically writes a PONG response to the socket and ignores the false return value from socket.write(), which is a backpressure signal, so a server that streams small PING frames while never reading the client's PONGs makes the outbound write queue and heap grow without bound until the Node.js process runs out of memory and terminates. The attack is remote and unauthenticated, needs only a normal WebSocket connection, and is asymmetric: small inbound PINGs produce a much larger retained outbound queue. Availability is the only impact. undici 5.x, 6.x, 7.x, and 8.x are affected; the WebSocket client was introduced in 5.15.0.
Patches
Upgrade to 6.29.1, 7.30.1, or 8.12.2, which pause WebSocket frame parsing when the automatic PONG response hits socket backpressure and resume on drain, bounding the outbound queue.
Workarounds
None.
Credited to benzdeus, UlisesGascon, mcollina.
Questions
- Does this affect the WebSocket global in Node.js?
Yes. The advisory names Node.js's bundled
globalThis.WebSocketas affected, since it is the undici client.- Does it affect servers that accept WebSocket connections?
The advisory describes the client receiver. The attacker is a malicious or compromised server, so exposure comes from outbound connections.
- Is there a workaround for CVE-2026-109932?
No. The advisory states none. Upgrade to 6.29.1, 7.30.1 or 8.12.2.
References
Read for this analysis:
- https://nvd.nist.gov/vuln/detail/CVE-2026-109932
- https://github.com/nodejs/undici/commit/39f93e142df03e559fe7c3d1fc7fba9beee2c185
- https://github.com/nodejs/undici/commit/53944624462b6797560288c55dbd8c66857bb495
- https://github.com/nodejs/undici/commit/b217373bb024cd93f85eb5b3ffd25684855f60f8
- https://cna.openjsf.org/security-advisories.html
- https://github.com/nodejs/undici/releases/tag/v6.29.1
- https://github.com/nodejs/undici/releases/tag/v7.30.1
- https://github.com/nodejs/undici/releases/tag/v8.12.2
- https://github.com/advisories/GHSA-9fm3-97px-rjf6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-109383
undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent
high7.4Oct 27, 2026CVE-2026-109829
undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects
high7.4Oct 27, 2026CVE-2026-109855
undici WebSocket client vulnerable to Denial of Service via failed HTTP/2 handshake
high7.5Oct 27, 2026CVE-2026-87018
undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation
high7.5Oct 27, 2026CVE-2026-87029
undici vulnerable to Denial of Service via unhandled exception in the decompress interceptor
medium5.9Oct 27, 2026CVE-2026-109841
undici vulnerable to Subresource Integrity bypass via non-lowercase algorithm tokens
medium5.9Oct 23, 2026
