CVE-2026-59725

Socket.IO: Engine.IO Polling Transport Connection Exhaustion

Published Jul 8, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-r635-g3xr-vw7x Socket.IO: Engine.IO Polling Transport Connection Exhaustion
History
Type Values Removed Values Added
First Time appeared Redhat
Redhat hummingbird
Weaknesses CWE-772
CPEs cpe:/a:redhat:hummingbird:1
Vendors & Products Redhat
Redhat hummingbird
References
Metrics threat_severity

None

threat_severity

Important

Type Values Removed Values Added
First Time appeared Socket
Socket socket.io
Vendors & Products Socket
Socket socket.io
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Socket.IO: Engine.IO Polling Transport Connection Exhaustion
Weaknesses CWE-404
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 14, 2026, 6:46 PM
Reserved
Jul 6, 2026, 3:34 PM
Status
Analyzed
Published
Jul 8, 2026, 4:16 PM
Modified
Oct 25, 2026, 8:10 PM
Severity
Important
Public date
Jul 8, 2026, 3:37 PM