Live › vulnerability › CVE-2026-109932
Go to dashboardThe undici WebSocket client, including Node.js's built-in globalThis.WebSocket, automatically answers every PING frame without respecting write backpressure. A malicious or compromised WebSocket server that sends small PINGs and never reads the PONGs makes the outbound queue grow until the process runs out of memory and crashes.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 19:04 UTC, 0h before NVD. All times on this page are UTC.
Applications that open WebSocket connections with undici or Node.js's built-in WebSocket client to servers that could be malicious or compromised are exposed. Versions from 5.15.0 onward are affected across the 5.x, 6.x, 7.x and 8.x lines, within the listed ranges. Services that use WebSockets only with trusted, fully controlled servers, or that do not use the WebSocket client at all, face much less risk.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| undici | npm | >= 5.15.0, < 6.29.1 | 6.29.1 |
| undici | npm | >= 7.0.0, < 7.30.1 | 7.30.1 |
| undici | npm | >= 8.0.0, < 8.12.2 | 8.12.2 |
| nodejs undici | vendor | >= 5.15.0, < 6.29.1 | 6.29.1 |
| nodejs undici | vendor | >= 7.0.0, < 7.30.1 | 7.30.1 |
| nodejs undici | vendor | >= 8.0.0, < 8.12.2 | 8.12.2 |
node -p "require('undici/package.json').version" in the project to see the installed undici versionnpm ls undici to find every copy, including ones pulled in transitivelyglobalThis.WebSocket or new WebSocket( in the code6.29.1 on the 6.x line, 7.30.1 on the 7.x line, or 8.12.2 on the 8.x lineglobalThis.WebSocketEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
undici is an HTTP client library for Node.js. In versions 5.15.0 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, its WebSocket client, including the bundled WebSocket exposed by Node.js, can be driven to exhaust process memory by a malicious or compromised WebSocket server. For every PING frame received, the client automatically writes a PONG response and ignores the backpressure signal from the socket write, 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, since small inbound PINGs produce a much larger retained outbound queue, with availability the only impact. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, which pause WebSocket frame parsing when the automatic PONG response hits socket backpressure and resume on drain, bounding the outbound queue, and users should upgrade to one of those versions or later. There is no workaround.
This page as .md · .json · in your agent: get_signal("CVE-2026-109932")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.