Vulnerability in Socketio Socket.io
CVE-2026-102599
Socket.IO enables bidirectional and low-latency communication for every platform. From Engine.IO 6.6.0 until 6.6.10, a transport upgrade can independently derive an Engine.IO protocol revision from the upgrade request instead of enforcing the revision stored on the existing session. A malicious client can establish a valid session and send an upgrade request with a different or omitted EIO query parameter, attaching a transport with incompatible parser and heartbeat behavior. A crafted heartbeat packet can then trigger an uncaught exception and terminate the Node.js process, including when Engine.IO v3 compatibility is disabled because an omitted EIO value is interpreted as revision 3 on the affected path. This issue is fixed in Engine.IO 6.6.10.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Socketio Socket.io — versions >= 6.6.0, < 6.6.10
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-102599?
- CVE-2026-102599 is a high-severity vulnerability in Socketio Socket.io, classified under CWE-248. CVSS score: 7.5/10. Published 2026-10-13.
- How severe is CVE-2026-102599?
- High severity. CVSS v3 base score is 7.5 out of 10.