cve.bz

CVE-2026-102599 socketio socket.io: Uncaught Exception

7.5 highEPSS 0.6%Fix available

High (7.5) in socketio socket.io. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in engine.io 6.6.10.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-248 Uncaught Exception
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • engine.io (npm): fixed in 6.6.10

Ask an AI about this CVE

Show the promptExplain CVE-2026-102599 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102599?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102599?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102599 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
socketio socket.io>= 6.6.0, < 6.6.10

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2gc4-cqfq-p2gvnpmengine.io>=6.6.0 <6.6.106.6.10

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw of IMPORTANT impact was found in the Engine.IO transport layer of Socket.IO. A remote, unauthenticated attacker can establish a valid Engine.IO session and then send a transport upgrade request with a mismatched or omitted EIO protocol revision parameter. Because the server derives the protocol revision for the upgrade from the request rather than enforcing the revision negotiated for the existing session, a transport with incompatible parser and heartbeat behavior is attached, and a subsequently crafted heartbeat packet can trigger an uncaught exception that terminates the Node.js process, causing a denial of service with no impact on confidentiality or integrity. The issue can be triggered even when Engine.IO v3 compatibility is disabled, because an omitted EIO value is interpreted as protocol revision 3 on the affected path. Within the Red Hat portfolio, only the community-supported qt6-qtwebengine package in EPEL is affected, and a fix is being pursued for it; Red Hat-managed products, including Red Hat Enterprise Linux, RHEL AI, Red Hat In-Vehicle OS, Red Hat JBoss Fuse, and Red Hat Hardened Images, are not affected because the vulnerable code is not present in the shipped versions of those components. The Red Hat severity of IMPORTANT matches the upstream assessment.

Red Hat's mitigation

Upgrading to an engine.io release that contains the fix (engine.io 6.6.10 or later, or a Socket.IO release that bundles it) is the recommended resolution. Where upgrading is not immediately possible, upstream documents workarounds that avoid the vulnerable transport-upgrade path: disable transport upgrades by setting allowUpgrades: false in the Socket.IO server options, or restrict the server to a single transport such as WebSocket-only via transports: ["websocket"]. Note that these options may affect client compatibility and connection behavior. As an additional temporary measure, deployments can reject Engine.IO requests for an existing session (sid) when the EIO query parameter is missing or does not match the protocol revision negotiated during the initial handshake; this is best implemented at the application proxy or middleware layer and only if the deployment can reliably track each session's negotiated protocol.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10grafanaNot affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gaudi-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-rocm-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/disk-image-cuda-rhel9Affected
Red Hat Fuse 7engine.ioNot affected
Red Hat Hardened Imagesgrafana12.4Not affected
Red Hat Hardened Imagesgrafana13.1Not affected
Red Hat Hardened Imagesgrafana13.2Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-102599.

References

Check your stackJSON