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.io/cluster-engine are not affected by this specific issue.
Affected versions:
@socket.io/cluster-engine@0.1.0The issue was fixed in:
@socket.io/cluster-engine@0.1.1If upgrading immediately is not possible, users can reduce exposure by:
These workarounds are defense-in-depth only. Upgrading to a patched version is recommended.
{
"cwe_ids": [
"CWE-20"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-05T23:44:21Z",
"nvd_published_at": "2026-09-29T16:17:06Z",
"severity": "HIGH"
}