Answer in brief
CVE-2026-102600 records a High severity (CVSS 7.5) vulnerability in Socket.IO: Prototype Pollution via Unsafe Client Session Lookup. The current sources do not mark it as known exploited. The current feed maps @socket.io/cluster-engine (generic), socketio/socket.io (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps @socket.io/cluster-engine (generic), socketio/socket.io (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @socket.io/cluster-enginegeneric | <0.1.1 | 0.1.1 |
| socketio/socket.iogeneric | <0.1.1 | 0.1.1 |
Published upstream
Sep 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 29, 2026
Socket.IO enables bidirectional and low-latency communication for every platform. Prior to 0.1.1, @socket.io/cluster-engine uses inherited object properties when looking up attacker-controlled session IDs in clustered deployments. Special property names such as __proto__ or constructor can resolve through the object prototype chain instead of identifying an actual connected client, causing the Node.js process to crash and resulting in denial of service. Applications that do not use @socket.io/cluster-engine are not affected. This issue is fixed in version 0.1.1.
Quoted source text, attributed separately from HOL analysis.