1vulnerability
- Critical0 (0.0%)
- High1 (100.0%)
- Medium0 (0.0%)
- Moderate0 (0.0%)
- Low0 (0.0%)
socket-io-cluster-engine
Ecosystem: npm
Downloads:
- 0CriticalAffects 0 versions
- 1HighAffects 1 version
- 0MediumAffects 0 versions
- 0ModerateAffects 0 versions
- 0LowAffects 0 versions
Monthly breakdown
- 1 vulnerabilities
- Critical: 0
- High: 1
- Medium: 0
- Moderate: 0
- Low: 0
Vulnerabilities (1)
Known vulnerabilities affecting socket-io-cluster-engine, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| GHSA-wfpm-5gcm-94cg | High | Socket.IO: Prototype Pollution via Unsafe Client Session Lookup### Impact This is a **prototype pollution / improper client lookup** vulnerability in `@socket.io/cluster-engine`. Servers using `@socket.io/cluster-engine` may be impacted when attacker-controlled session IDs are processed in clustered deployments. A malicious client could use special property names such as `__proto__`, `constructor`, or other inherited object keys as a session identifier, causing the server to read properties from the object prototype chain instead of only real connected clients. The impact is **denial of service** through process crash. Applications not using `@socket. |
| GitHub (opens in a new tab) |
- GHSA-wfpm-5gcm-94cgHighSocket.IO: Prototype Pollution via Unsafe Client Session Lookup
< 0.1.1
### Impact This is a **prototype pollution / improper client lookup** vulnerability in `@socket.io/cluster-engine`. Servers using `@socket.io/cluster-engine` may be impacted when attacker-controlled session IDs are processed in clustered deployments. A malicious client could use special property names such as `__proto__`, `constructor`, or other inherited object keys as a session identifier, causing the server to read properties from the object prototype chain instead of only real connected clients. The impact is **denial of service** through process crash. Applications not using `@socket.
CVE: CVE-2026-102600