CVE-2026-59725

Socket.IO: Engine.IO Polling Transport Connection Exhaustion

HIGH
7.5
CVSS Score
Published: July 8, 2026 at 03:37 PM UTC
Updated: October 25, 2026 at 08:10 PM UTC
3 products affected across 2 vendorsEngine.ioEngine.ioSocket.IO

Using socket.io by socketio?

Get instant alerts when new vulnerabilities affect socket.io - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.1.0 ≤ v < 6.6.7
Affected range stops below 6.6.7, so it looks safe — our inference, not a vendor statement
v < 6.6.7
Affected range stops below 6.6.7, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-404

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card