CVE-2026-59725: Socket.IO: Engine.IO Polling Transport Connection Exhaustion
Impact
An unauthenticated remote attacker can cause a denial of service in affected versions of engine.io by opening Engine.IO polling sessions and sending an invalid binary POST request with:
Content-Type: application/octet-stream
against an Engine.IO protocol v4 polling transport.
In the vulnerable code path, the server reports a transport error but does not properly close the HTTP response associated with the malformed request. As a result, the underlying HTTP connection may remain open, consuming one server-side socket/resource per crafted request.
An attacker can repeat this with many sessions to exhaust available HTTP connections, sockets, file descriptors, or related server resources, potentially preventing legitimate clients from connecting.
Patches
The issue was fixed in:
- engine.io 6.6.7
The fix ensures that invalid binary polling POST requests are explicitly rejected with an HTTP response and closed properly.
Users should upgrade to:
sh npm install engine.io@^6.6.7
or a later fixed version.
If using Socket.IO through the monorepo/packages, update to a Socket.IO release that depends on a fixed engine.io version.
Workarounds
If upgrading immediately is not possible, possible mitigations include:
- Block or reject polling POST requests with Content-Type: application/octet-stream for Engine.IO protocol v4 at a reverse proxy, load balancer, WAF, or application middleware. - Disable HTTP long-polling if your deployment can use WebSocket-only transport. - Enforce strict request/connection timeouts at the HTTP server, reverse proxy, or load balancer. - Apply per-IP rate limits and connection limits for Engine.IO endpoints. - Restrict access to the Socket.IO/Engine.IO endpoint where feasible.
Example Socket.IO configuration to disable polling, if compatible with your clients:
js const io = new Server(httpServer, { transports: ["websocket"], });
References
- Fix commit: https://github.com/socketio/socket.io/commit/fc11285e14964c2132d122164bf130c355f60671 - 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 - socket.io repository: https://github.com/socketio/socket.io - engine.io package: https://www.npmjs.com/package/engine.io
Other sources
Socket.IO enables bidirectional and low-latency communication for every platform. From 4.1.0 before 6.6.7, Engine.IO protocol v4 polling transport does not properly close the HTTP response for invalid binary POST requests with Content-Type: application/octet-stream, allowing an unauthenticated attacker to exhaust server-side connections and sockets. This issue is fixed in version 6.6.7.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/engine.ioto a version that resolves this vulnerability.Fixed in 6.6.7 - Upgrade
Upgrade
engine.ioto a version that resolves this vulnerability.Fixed in 6.6.7 - Configuration
If compatible with your clients, disable Engine.IO polling by configuring Socket.IO Server with transports: ["websocket"] (so only WebSocket transport is used).
Socket.IO/Engine.IO server (Node.js) transports = ["websocket"] - Compensating control
At a reverse proxy, load balancer, WAF, or application middleware, block or reject Engine.IO protocol v4 polling POST requests that have Content-Type: application/octet-stream.
- Compensating control
Apply per-IP rate limits and connection limits for Engine.IO endpoints to reduce the impact of connection/socket exhaustion.
- Compensating control
Enforce strict request/connection timeouts at the HTTP server, reverse proxy, or load balancer to prevent malformed requests from keeping connections open too long.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-59725?
The severity of CVE-2026-59725 is classified as high with a score of 7.5.
How do I fix CVE-2026-59725?
To fix CVE-2026-59725, update to Socket.IO Engine.IO protocol version 6.6.7 or later.
What vulnerability does CVE-2026-59725 describe?
CVE-2026-59725 describes a connection exhaustion vulnerability in the Engine.IO polling transport of Socket.IO.
Who is affected by CVE-2026-59725?
Any application using Socket.IO versions from 4.1.0 to 6.6.6 that utilizes the Engine.IO protocol v4 polling transport is affected by CVE-2026-59725.
What kind of attacks can CVE-2026-59725 enable?
CVE-2026-59725 can enable unauthenticated denial-of-service attacks due to improper handling of invalid binary POST requests.