NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-59724: Socket.IO: Engine.IO WebTransport SID DoS

highCVSS 3.1 7.5GHSA-gr94-w7qr-f4j3

Impact Engine.IO servers with WebTransport enabled are vulnerable to a remotely triggerable denial of service. A malicious unauthenticated client can send a crafted WebTransport upgrade request containing a specially chosen session ID, such as proto.

Published Aug 31, 2026

Affected packages

engine.io

Ecosystem
npm
Affected
>= 6.5.0, < 6.6.7
Fixed in
6.6.7
Check
npm ls engine.io

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

Engine.IO servers with WebTransport enabled are vulnerable to a remotely triggerable denial of service.

A malicious unauthenticated client can send a crafted WebTransport upgrade request containing a specially chosen session ID, such as __proto__. Because the session ID lookup did not properly verify that the key was an own property of the clients object, the lookup could resolve to an inherited prototype property instead of a valid Engine.IO client.

This can cause a TypeError during WebTransport upgrade handling. Since the failure occurs in an asynchronous context, it may result in an unhandled Promise rejection and terminate the Node.js process on affected Node.js versions/configurations.

Successful exploitation can allow an unauthenticated remote attacker to crash the server process and cause denial of service. Under a process supervisor, repeated exploitation may cause crash loops.

Affected configurations are limited to deployments where WebTransport support is enabled. WebTransport is not enabled by default.

Affected versions:

  • engine.io >= 6.5.0 < 6.6.7

Patches

The issue was fixed in:

  • engine.io 6.6.7

Users should upgrade to [email protected] or later.

If using Socket.IO packages that depend on Engine.IO, users should update to a Socket.IO release that includes the patched Engine.IO version.

Workarounds

If upgrading immediately is not possible, affected users can mitigate the issue by disabling WebTransport support.

WebTransport is opt-in, so servers should ensure that webtransport is not included in the enabled transports list.

For example, use only the default HTTP long-polling and WebSocket transports:

const engine = new Server({
  transports: ["polling", "websocket"],
});

Additional operational mitigations may include:

  • Restricting access to WebTransport endpoints at the reverse proxy or HTTP/3 layer.
  • Disabling HTTP/3/WebTransport support until the patched version can be deployed.
  • Running the service under a supervisor as a partial availability mitigation, though this does not prevent repeated crash attempts.

References

  • Fix commit: https://github.com/socketio/socket.io/commit/1fa1f46cd420ac5b57bb4c04c959b58f3c79158c
  • Engine.IO changelog entry for 6.6.7: https://github.com/socketio/socket.io/blob/main/packages/engine.io/CHANGELOG.md#667-2026-04-27
  • Engine.IO package: https://www.npmjs.com/package/engine.io
  • Socket.IO repository: https://github.com/socketio/socket.io

Credited to ni8walk3r.

References

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. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries