CVE-2026-59725: Socket.IO: Engine.IO Polling Transport Connection Exhaustion

Published Jul 8, 2026
·
Updated

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

3 affected componentsFixes available
Socket.IO Engine.IO protocol v4 polling transport>4.1.0<6.6.7
Socket Engine.io Node.js>=4.1.0<6.6.7
npm/engine.io>=4.1.0<6.6.7
6.6.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/engine.io to a version that resolves this vulnerability.

    Fixed in 6.6.7
  2. Upgrade

    Upgrade engine.io to a version that resolves this vulnerability.

    Fixed in 6.6.7
  3. 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"]
  4. 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.

  5. Compensating control

    Apply per-IP rate limits and connection limits for Engine.IO endpoints to reduce the impact of connection/socket exhaustion.

  6. 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

Jul 8, 2026
CVE Published
via MITRE·03:37 PM
Data Sourced
via MITRE·03:37 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 20, 2026
Advisory Published
via GitHub·09:49 PM
Data Sourced
via GitHub·09:49 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-59725?

The severity of CVE-2026-59725 is classified as high with a score of 7.5.

2

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.

3

What vulnerability does CVE-2026-59725 describe?

CVE-2026-59725 describes a connection exhaustion vulnerability in the Engine.IO polling transport of Socket.IO.

4

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.

5

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.

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
CVE-2026-59725 - Socket.IO: Engine.IO Polling Transport Connection Exhaustion - SecAlerts