Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-2gc4-cqfq-p2gv | Socket.IO: Engine.IO Protocol Revision Mismatch DoS |
Tue, 13 Oct 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Socket.IO: Engine.IO Protocol Revision Mismatch DoS | |
| Weaknesses | CWE-248 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-13T19:05:10.870Z
Reserved: 2026-09-29T14:18:02.920Z
Link: CVE-2026-102599
No data.
Status : Awaiting Analysis
Published: 2026-10-13T19:17:49.037
Modified: 2026-10-13T19:25:38.150
Link: CVE-2026-102599
No data.
OpenCVE Enrichment
No data.
Github GHSA