CVE-2026-59724: socketio socket.io · Improper Input Validation
Affects socketio socket.ioSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 6.6.7 soon.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.6.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade socketio socket.io to 6.6.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| socketiosocket.io | Affected
| Fixed in
|
npmsocket.iopkg:npm/socket.ioOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade socket.io to version 6.6.7 or later where this issue is fixed. Patch status is confirmed by the vendor advisory indicating the fix in 6.6.7. No additional mitigations are specified.
Description
Socket.IO enables bidirectional and low-latency communication for every platform. From 6.5.0 before 6.6.7, Engine.IO servers with WebTransport enabled can resolve a crafted session ID such as __proto__ through an inherited property of the clients object during WebTransport upgrade handling, causing a TypeError and denial of service. This issue is fixed in version 6.6.7.