Impact
A specially crafted packet to the Socket.IO framework can force the server to wait for a large number of binary attachments and buffer them. The result is an out‑of‑memory condition that stops the server from processing new requests and effectively brings the service offline. This weakness is a classic memory exhaustion flaw and falls under CWE‑770. The impact is a denial of service, compromising availability rather than confidentiality or integrity.
Affected Systems
Socket.IO, versions prior to 3.3.5, 3.4.4, and 4.2.6, regardless of the underlying Node.js runtime. The affected component is the Socket.IO parser module, which accepts client packets over WebSocket or HTTP.
Risk and Exploitability
The issue carries a high severity CVSS score of 8.7. Its exploit probability is low (EPSS < 1%) and it is not listed in the CISA KEV catalog. The vulnerability is remotely accessible; an attacker only needs send a malicious packet over an open Socket.IO connection, without authentication. If exploited, the server would exhaust its memory pool, leading to a service crash or refusal to accept further requests.
OpenCVE Enrichment
Github GHSA