This page lists publicly disclosed CVE vulnerabilities affecting socket socket.io-parser (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2026-33151 | Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. Prior to versions 3.3.5, 3.4.4, and 4.2.6, a specially crafted Socket.IO packet can make the server wait for a large number of binary attachments and buffer them, which can be exploited to make the server run out of memory. This issue has been patched in versions 3.3.5, 3.4.4, and 4.2.6. | [email protected] | 8.7 | 0.06% | 2026-03-20 | 2026-04-14 |
| CVE-2023-32695 | socket.io parser is a socket.io encoder and decoder written in JavaScript complying with version 5 of socket.io-protocol. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. A patch has been released in version 4.2.3. | [email protected] | 7.3 | 0.30% | 2023-05-27 | 2024-11-21 |
| CVE-2022-2421 | Due to improper type validation in attachment parsing the Socket.io js library, it is possible to overwrite the _placeholder object which allows an attacker to place references to functions at arbitrary places in the resulting query object. | [email protected] | 10.0 | 0.76% | 2022-10-26 | 2026-02-06 |
| CVE-2020-36049 | socket.io-parser before 3.4.1 allows attackers to cause a denial of service (memory consumption) via a large packet because a concatenation approach is used. | [email protected] | 7.5 | 0.53% | 2021-01-08 | 2024-11-21 |