Server crash via inherited WebTransport SID lookup
Published Jul 8, 2026 · Updated Jul 8, 2026
Improper input validation in Socket.IO Engine.IO 6.5.0 through 6.6.6 allows remote attackers to crash WebTransport-enabled servers. The WebTransport upgrade handler accepts a truthy SID without requiring an own key of the clients object, so proto resolves through the prototype chain and triggers a TypeError. WebTransport is opt-in; the asynchronous failure can terminate affected Node.js processes or produce repeated crash loops under a supervisor.
Summary
What happened
Improper input validation in Socket.IO Engine.IO 6.5.0 through 6.6.6 allows remote attackers to crash WebTransport-enabled servers. The WebTransport upgrade handler accepts a truthy SID without requiring an own key of the clients object, so proto resolves through the prototype chain and triggers a TypeError. WebTransport is opt-in; the asynchronous failure can terminate affected Node.js processes or produce repeated crash loops under a supervisor.
The record
- CVE
- CVE-2026-59724
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- Socket.IO
- Product
- Socket.IO
- Classifications
- CWE-20, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 6.5.0, < 6.6.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo