Advisory

GHSA-wfpm-5gcm-94cg

Also known as: CVE-2026-102600

Summary

Socket.IO: Prototype Pollution via Unsafe Client Session Lookup

Details

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.io/cluster-engine are not affected by this specific issue.

Affected versions:

Patches

The issue was fixed in:

Workarounds

If upgrading immediately is not possible, users can reduce exposure by:

  • Rejecting or sanitizing suspicious session IDs before they reach the cluster engine.
  • Running the cluster engine behind trusted infrastructure that prevents arbitrary clients from crafting raw Engine.IO session-related requests.

These workarounds are defense-in-depth only. Upgrading to a patched version is recommended.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-10-05 23:44 UTC
Modified
2026-10-06 00:00 UTC

Affected packages and fixes

@socket.io/cluster-engine

npm · All systems

Affected

  • introduced 0, fixed 0.1.1 (semver)

Fixed versions

0.1.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences