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.
Published: 2026-07-08
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Socket.IO’s Engine.IO component allows WebTransport sessions to be upgraded using a session ID supplied by the client. Between versions 6.5.0 and 6.6.6 the upgrade routine resolves the supplied ID against an internal clients object without validating that the identifier is a safe property name. If an attacker supplies a crafted value such as "__proto__", the lookup triggers a TypeError, crashing the upgrade handling and causing a denial of service. The flaw is an input validation weakness (CWE‑20) and a type confusion issue (CWE‑843).

Affected Systems

The vulnerability affects Socket.IO Engine.IO servers configured with WebTransport enabled and running versions between 6.5.0 and 6.6.6 inclusive. The fix was introduced in Engine.IO version 6.6.7, so any installation of 6.6.7 or newer is not affected. The problem resides exclusively in the server side; client‑side components are not impacted.

Risk and Exploitability

The CVSS score of 7.5 indicates high severity, while an EPSS score of less than 1% suggests a very low current probability of exploitation. The vulnerability is not listed in CISA’s KEV catalog. An attacker can exploit it remotely by sending a WebTransport upgrade request containing a malicious session identifier such as "__proto__", which causes the server to throw an exception and drop the connection. Because the defect lies in the server’s internal state handling, repeated attacks can result in service interruption until the vulnerable code path is removed.

Generated by OpenCVE AI on July 29, 2026 at 13:58 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Socket.IO framework to version 6.6.7 or newer
  • Disable WebTransport in the Engine.IO configuration to eliminate the vulnerable code path
  • Implement server‑side rate limiting or connection throttling to reduce the impact of repeated denial‑of‑service attempts

Generated by OpenCVE AI on July 29, 2026 at 13:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 10 Jul 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-843
References
Metrics threat_severity

None

threat_severity

Important


Fri, 10 Jul 2026 09:30:00 +0000

Type Values Removed Values Added
First Time appeared Socket
Socket socket.io
Vendors & Products Socket
Socket socket.io

Wed, 08 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 08 Jul 2026 15:45:00 +0000

Type Values Removed Values Added
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.
Title Socket.IO: Engine.IO WebTransport SID DoS
Weaknesses CWE-20
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

Socket Socket.io
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-08T19:41:18.905Z

Reserved: 2026-07-06T15:34:16.916Z

Link: CVE-2026-59724

cve-icon Vulnrichment

Updated: 2026-07-08T17:58:47.574Z

cve-icon NVD

No data.

cve-icon Redhat

Severity : Important

Publid Date: 2026-07-08T15:35:39Z

Links: CVE-2026-59724 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-07-29T14:00:03Z

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-843

    Access of Resource Using Incompatible Type ('Type Confusion')