Cpe:2.3:a:socket.io:cluster-Engine:0.1.0:*:*:*:*:node.js:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3asocket.iocluster-engine0.1.0node.js/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 06 Oct 2026 00:45:04 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgPrototype Pollution in @socket.io/cluster-enginehttps://feed.craftedsignal.io/briefs/2026-10-socketio-prototype-pollution/Tue, 06 Oct 2026 00:45:04 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-socketio-prototype-pollution/The @socket.io/cluster-engine package is vulnerable to prototype pollution when processing attacker-controlled session IDs, allowing an attacker to cause a denial of service via process crash.The @socket.io/cluster-engine package, used for managing socket connections in clustered environments, contains a prototype pollution vulnerability (CVE-2026-102600) in version 0.1.0. The vulnerability exists due to unsafe handling of client-provided session identifiers during the lookup process. An attacker can craft requests using special property names, such as 'proto' or 'constructor', as session identifiers. Because the engine incorrectly treats these keys as valid session lookups, it attempts to access properties from the object prototype chain rather than the expected client storage objects. This unexpected state leads to internal server errors and, ultimately, a process crash, effectively resulting in a denial-of-service condition for affected Node.js applications. This issue specifically affects deployments utilizing the cluster-engine component.

Impact

The vulnerability results in a denial of service (DoS) by crashing the Node.js process hosting the @socket.io/cluster-engine. This impact is significant for real-time applications relying on persistent socket connections, as the crash disrupts all connected clients on that process.

Recommendation

  • Upgrade the @socket.io/cluster-engine package to version 0.1.1 or later to remediate CVE-2026-102600.
  • Implement input validation on session identifiers in custom middleware to reject keys containing 'proto', 'constructor', or 'prototype' before passing them to the cluster engine as a defense-in-depth measure.
]]>lowadvisorynodejsvulnerabilityprototype-pollutiondos