Socket.io-parser
4 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Socket.io-parser, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Socket.io-parser CVEs per month
| Month | CVEs |
|---|---|
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 1 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
| 2026-10 | 0 |
Severity
How the 4 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- Critical1
- High3
Latest CVEs
The 4 most recently published vulnerabilities affecting Socket.io-parser.
- CVE-2026-33151socket.io allows an unbounded number of binary attachments7.5
- CVE-2023-32695Insufficient validation when decoding a Socket.IO packet7.3
- CVE-2022-2421Socket.io - Improper type validation in attachment parsing10.0
- CVE-2020-36049socket.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.7.5
Product grouping is registry-driven, with AI assist and human review. How it works