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.
Published: 2026-10-13
Score: 7.5 High
EPSS: n/a
KEV: No
Impact: Denial of Service
Action: Update
AI Analysis

Impact

The vulnerability allows an attacker to initiate a transport upgrade that derives a different Engine.IO protocol revision than the one stored in the existing session. By sending a crafted upgrade request and a specially designed heartbeat packet, the malicious client can trigger an uncaught exception and terminate the Node.js process. This results in a denial of service to all clients connected to the affected Socket.IO instance.

Affected Systems

Socket.IO Engine.IO library versions 6.6.0 through 6.6.10 are impacted. The flaw applies to deployments that use any transport upgrade path without enforcing the stored protocol revision.

Risk and Exploitability

The CVSS score of 7.5 indicates moderate risk, while the EPSS score is unavailable, providing no clear evidence of high exploitation probability. The flaw is not listed in the CISA KEV catalog. The likely attack vector is a remote client able to communicate over the network and send crafted upgrade requests, which is inferred from the nature of the vulnerability. If exploited, the attacker can bring the Node.js process down, causing interruption of service for all users.

Generated by OpenCVE AI on October 13, 2026 at 21:48 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Engine.IO to version 6.6.10 or later
  • Configure the Socket.IO server to enforce the session’s protocol revision during transport upgrades
  • Implement Node.js process monitoring to detect and restart the service upon unexpected termination

Generated by OpenCVE AI on October 13, 2026 at 21:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-2gc4-cqfq-p2gv Socket.IO: Engine.IO Protocol Revision Mismatch DoS
History

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

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


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-13T19:05:10.870Z

Reserved: 2026-09-29T14:18:02.920Z

Link: CVE-2026-102599

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-13T19:17:49.037

Modified: 2026-10-13T19:25:38.150

Link: CVE-2026-102599

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-13T22:00:25Z

Weaknesses