CVE-2026-109932: undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering

Published Oct 15, 2026
·
Updated

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.

Other sources

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.

— Ubuntu

Affected Software

14 affected componentsFixes available
npm/undici>=5.15.0<=6.29.0, >=7.0.0<=7.30.0, >=8.0.0<=8.12.1
Nodejs Undici Node.js>=5.15.0<6.29.1
Nodejs Undici Node.js>=7.0.0<7.30.1
Nodejs Undici Node.js>=8.0.0<8.12.2
npm/undici>=8.0.0<8.12.2
8.12.2
npm/undici>=7.0.0<7.30.1
7.30.1
npm/undici>=5.15.0<6.29.1
6.29.1
ubuntu/node-undici*
ubuntu/node-undici*
ubuntu/node-undici*
debian/node-undici<=5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4, <=5.15.0+dfsg1+~cs20.10.9.3-1+deb12u3, <=7.3.0+dfsg1+~cs24.12.11-1
8.12.2+dfsg+~cs3.2.3-2
debian/node-undici*
debian/node-undici*
debian/node-undici<8.12.2+dfsg+~cs3.2.3-1
8.12.2+dfsg+~cs3.2.3-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/undici to a version that resolves this vulnerability.

    Fixed in 8.12.2
  2. Upgrade

    Upgrade npm/undici to a version that resolves this vulnerability.

    Fixed in 7.30.1
  3. Upgrade

    Upgrade npm/undici to a version that resolves this vulnerability.

    Fixed in 6.29.1
  4. Upgrade

    Upgrade debian/node-undici to a version that resolves this vulnerability.

    Fixed in 8.12.2+dfsg+~cs3.2.3-2
  5. Upgrade

    Upgrade debian/node-undici to a version that resolves this vulnerability.

    Fixed in 8.12.2+dfsg+~cs3.2.3-1
  6. Upgrade

    Upgrade undici to a version that resolves this vulnerability.

    Fixed in 6.29.1
  7. Upgrade

    Upgrade undici to a version that resolves this vulnerability.

    Fixed in 7.30.1
  8. Upgrade

    Upgrade undici to a version that resolves this vulnerability.

    Fixed in 8.12.2

Event History

Oct 15, 2026
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·06:44 PM
Data Sourced
via MITRE·06:44 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·07:17 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeaknessAffected Software
Oct 27, 2026
Advisory Published
via GitHub·07:02 PM
Data Sourced
via GitHub·07:02 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this denial-of-service condition?

Deployments using the undici WebSocket client in versions 5.15.0 through 6.29.0, 7.0.0 through 7.30.0, or 8.0.0 through 8.12.1 are affected. This also includes the bundled WebSocket exposed by Node.js where it uses an affected undici version.

2

What must an attacker do to trigger the issue?

An attacker needs only a normal WebSocket connection to a client that connects to a malicious or compromised WebSocket server. The server sends small PING frames continuously while not reading the automatic PONG responses, causing the client's outbound queue and heap to grow until the process terminates.

3

Is there a mitigation if upgrading cannot happen immediately?

No workaround is provided. Upgrade undici to 6.29.1, 7.30.1, or 8.12.2 or later, depending on the affected release line.

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