npm package report

Is @socket.io/cluster-engine safe?

1 known vulnerability, worst severity HIGH.

// reach

0 direct dependencies

none carry a known advisory

    0 packages depend on it

    an advisory here reaches each of them

      Create a free accountfor every dependency path, dependent and what to upgrade
      // ai model usage

      Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

      cvss
      0.0
      high

      severity out of 10

      epss
      0.00%
      low

      chance of exploitation in 30 days, 28th percentile of all CVEs

      xyz score
      not scored

      CyberXYZ composite out of 10

      fig. 01 — GHSA-wfpm-5gcm-94cg, the advisory selected below

      // 1 advisories

      GHSA-wfpm-5gcm-94cg

      HIGHCVE-2026-102600
      // 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.

      // cvss v3.1 vector

      CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

      Attack vector
      Network
      Attack complexity
      Low
      Privileges required
      None
      User interaction
      None
      Scope
      Unchanged
      Confidentiality
      None
      Integrity
      None
      Availability
      High

      Checked 2026-10-06 at 02:01 UTC. The most recent advisory here was published 2026-10-05. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.