Skip to main content
VulnerabilityPublished

CVE-2026-102600: socketio socket.io · Improper Input Validation

Affects socketio socket.ioSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 0.1.1 soon.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.1.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade socket.io and cluster-engine to 0.1.1.

Affected software

ProductAffectedFixed in
socketiosocket.ioAffected
  • <0.1.1
Fixed in
  • 0.1.1
@socket.iocluster-engineAffected
  • <0.1.1
Fixed in
  • 0.1.1

AI-suggested

Upgrade to @socket.io/cluster-engine version 0.1.1 or later, where this vulnerability is fixed. Applications not using @socket.io/cluster-engine are not affected and require no action.

Description

Socket.IO enables bidirectional and low-latency communication for every platform. Prior to 0.1.1, @socket.io/cluster-engine uses inherited object properties when looking up attacker-controlled session IDs in clustered deployments. Special property names such as __proto__ or constructor can resolve through the object prototype chain instead of identifying an actual connected client, causing the Node.js process to crash and resulting in denial of service. Applications that do not use @socket.io/cluster-engine are not affected. This issue is fixed in version 0.1.1.

References

Community reviews

Loading reviews…