CVE-2026-102599: Engine.io Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-2gc4-cqfq-p2gv
CVSS 7.5
CWE-248
Published
Advisory Summary

CVE-2026-102599 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-248: Uncaught Exception) affecting Engine.io libraries in the npm ecosystem. The issue involves engine.io protocol revision mismatch dos. Remediation is available by upgrading affected packages to version 6.6.10.

CVE-2026-102599 at a Glance

CVE Identifier CVE-2026-102599
GHSA Identifier GHSA-2gc4-cqfq-p2gv
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-248: Uncaught Exception
Affected Product Engine.io
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-102599

To remediate this vulnerability, upgrade all affected Engine.io dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

engine.io fixed: 6.6.10
npm install engine.io@6.6.10
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls engine.io

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-102599, inspect your project dependencies using npm:

npm ls engine.io

Analyze the terminal output to locate any version of Engine.io in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.6.10), your application is affected.

Note: The npm ls engine.io command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-248: Uncaught Exception, where an exception is thrown from a function, but it is not caught. In Engine.io, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact A denial-of-service vulnerability exists in Engine.IO / Socket.IO servers that allow transport upgrades. The Engine.IO protocol revision is negotiated during the initial handshake and stored on the session, but a newly-created transport, including a WebSocket upgrade transport, could independently derive a different protocol revision from the upgrade request query parameters. The server did not verify that the protocol revision of an upgrade request matched the protocol revision of the existing session. A malicious client could exploit this mismatch by establishing a valid Engine.IO session and then sending an upgrade request with a different, or omitted, `EIO` query parameter. This could cause the server to attach a transport using a parser and heartbeat behavior inconsistent with the session. Under some conditions, a crafted heartbeat packet could trigger an uncaught exception and terminate the Node.js process. Servers using the default Engine.IO v4 protocol are impacted. The issue can be triggered even when Engine.IO v3 compatibility is disabled, because an omitted `EIO` parameter is interpreted as protocol v3 on the affected transport path. The impact is **denial of service** through process crash. Affected versions: - `engine.io >= 6.6.0, < 6.6.10` ## Patches The issue was fixed in: - **engine.io 6.6.10** Users should upgrade to `engine.io@6.6.10` or later. If using Socket.IO packages that depend on Engine.IO, users should update to a Socket.IO release that includes the patched Engine.IO version. ### Workarounds If upgrading is not immediately possible, users can reduce exposure by disabling transport upgrades: ```javascript const io = new Server(httpServer, { allowUpgrades: false }); ``` or by allowing only a single transport, for example WebSocket only: ```javascript const io = new Server(httpServer, { transports: ["websocket"] }); ``` These mitigations avoid the vulnerable upgrade path, but they may affect client compatibility and connection behavior. As an additional temporary mitigation, deployments may reject Engine.IO requests for an existing `sid` when the `EIO` query parameter is missing or does not match the protocol revision used during the initial handshake. This is best done at the application proxy or middleware layer only if the deployment can reliably track the session’s negotiated protocol. Upgrading remains the recommended fix.

CVE-2026-102599 Affected Engine.io Versions

1 component(s)
Fixed Versions:
6.6.10
Product / Package Ecosystem Affected Versions Fixed Version
engine.io
npm
≥ 6.6.0
< 6.6.10
6.6.10

References

Frequently Asked Questions

What is CVE-2026-102599?
CVE-2026-102599 is a security vulnerability in Engine.io involving Engine.IO Protocol Revision Mismatch DoS under CWE-248: Uncaught Exception.
Which Engine.io versions are affected?
Affected versions include releases prior to 6.6.10 across affected packages: engine.io.
What version fixes CVE-2026-102599?
Upgrading to 6.6.10 (or the latest patched release for your respective branch) resolves the vulnerability.
Is engine.io affected?
Yes, engine.io is affected in releases prior to 6.6.10. Upgrade your dependency to 6.6.10 or later.
What is the CVSS score of CVE-2026-102599?
CVE-2026-102599 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-102599?
CVE-2026-102599 is classified under CWE-248: Uncaught Exception (An exception is thrown from a function, but it is not caught.).
How can I check npm dependencies for CVE-2026-102599?
Run the dependency tree command: 'npm ls engine.io'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2gc4-cqfq-p2gv",
  "modified" : "2026-09-29T23:44:33Z",
  "published" : "2026-09-29T23:44:33Z",
  "aliases" : [ "CVE-2026-102599" ],
  "summary" : "Socket.IO: Engine.IO Protocol Revision Mismatch DoS",
  "details" : "### Impact\n\nA denial-of-service vulnerability exists in Engine.IO / Socket.IO servers that allow transport upgrades.\n\nThe Engine.IO protocol revision is negotiated during the initial handshake and stored on the session, but a newly-created transport, including a WebSocket upgrade transport, could independently derive a different protocol revision from the upgrade request query parameters. The server did not verify that the protocol revision of an upgrade request matched the protocol revision of the existing session.\n\nA malicious client could exploit this mismatch by establishing a valid Engine.IO session and then sending an upgrade request with a different, or omitted, `EIO` query parameter. This could cause the server to attach a transport using a parser and heartbeat behavior inconsistent with the session. Under some conditions, a crafted heartbeat packet could trigger an uncaught exception and terminate the Node.js process.\n\nServers using the default Engine.IO v4 protocol are impacted. The issue can be triggered even when Engine.IO v3 compatibility is disabled, because an omitted `EIO` parameter is interpreted as protocol v3 on the affected transport path.\n\nThe impact is **denial of service** through process crash.\n\nAffected versions:\n\n- `engine.io >= 6.6.0, < 6.6.10`\n\n## Patches\n\nThe issue was fixed in:\n\n- **engine.io 6.6.10**\n\nUsers should upgrade to `engine.io@6.6.10` or later.\n\nIf using Socket.IO packages that depend on Engine.IO, users should update to a Socket.IO release that includes the patched Engine.IO version.\n\n### Workarounds\n\nIf upgrading is not immediately possible, users can reduce exposure by disabling transport upgrades:\n\n```javascript\nconst io = new Server(httpServer, {\n  allowUpgrades: false\n});\n```\n\nor by allowing only a single transport, for example WebSocket only:\n\n```javascript\nconst io = new Server(httpServer, {\n  transports: [\"websocket\"]\n});\n```\n\nThese mitigations avoid the vulnerable upgrade path, but they may affect client compatibility and connection behavior.\n\nAs an additional temporary mitigation, deployments may reject Engine.IO requests for an existing `sid` when the `EIO` query parameter is missing or does not match the protocol revision used during the initial handshake. This is best done at the application proxy or middleware layer only if the deployment can reliably track the session’s negotiated protocol.\n\nUpgrading remains the recommended fix.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "engine.io"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "6.6.0"
      }, {
        "fixed" : "6.6.10"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/socketio/socket.io/security/advisories/GHSA-2gc4-cqfq-p2gv"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/socketio/socket.io/commit/86db1fc3db2cd315a065d64c4e48918ccf9b4729"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/socketio/socket.io"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/socketio/socket.io/releases/tag/engine.io@6.6.10"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-248" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-29T23:44:33Z",
    "nvd_published_at" : null
  }
}