CVE-2026-102599

The record

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.

Affected packages

Related vulnerabilities

• CVE-2026-100347 kin-openapi is a Go project for handling OpenAPI files. CWE-248
• CVE-2026-107382 MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB… CWE-248
• CVE-2026-106122 The RabbitMQ Java client library allows Java and JVM-based applications to connect to and… CWE-248
• CVE-2026-105757 vLLM is an inference and serving engine for large language models. CWE-248
• CVE-2026-105756 vLLM is an inference and serving engine for large language models. CWE-248
• CVE-2026-103387 A weakness has been identified in garycourt uri-js up to 4.4.1. CWE-248
• CVE-2026-102281 Nest is a framework for building scalable Node.js server-side applications. CWE-248
• CVE-2026-101918 PyJWT is a Python implementation of JSON Web Token standards. CWE-248