CVE-2026-102600: Socket.IO: Prototype Pollution via Unsafe Client Session Lookup
socketio · socket.io
Affected: socketio socket.io · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 32% of scored CVEs
DescriptionCVE.org
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.
Affected products2
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- socketio · socket.io< 0.1.1
- @socket.io · cluster-engine< 0.1.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- socketio
- Published
- September 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-102600 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.