Vulnerability in @socket.io/cluster-engine (CVE-2026-102600)
Summary
Vulnerability in @socket.io/cluster-engine (CVE-2026-102600). Risk of unauthorized operations or information disclosure. Exploitable via __proto__. Mitigation: upgrade to 0.1.1 or later.
Original description
The description as published by the source.
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:
@socket.io/cluster-engine@0.1.0
Patches
The issue was fixed in:
@socket.io/cluster-engine@0.1.1
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-102600 has been found in @socket.io/cluster-engine.
Attackers can target a specific entry point like __proto__ over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade @socket.io/cluster-engine to 0.1.1 or later.
If unsure, ask your IT team or search "@socket.io/cluster-engine CVE-2026-102600" on the vendor's site.
CVE-2026-102600 (@socket.io/cluster-engine) — CWE-20 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: __proto__ / constructor
Patched: 0.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in @socket.io/cluster-engine. Attackers reach the vulnerable code path via __proto__ without authentication.
Check the vendor advisory for the affected versions of @socket.io/cluster-engine. Attack surface: __proto__ / constructor.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 0.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@socket.io/cluster-engine' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@socket.io/cluster-engine' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@socket.io/cluster-engineを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @socket.io/cluster-engine to 0.1.1ステージング環境で 0.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com