# socket.io-parser (npm) vulnerabilities 5 known vulnerabilities (1 critical, 3 high), with the versions each affects and the releases that fix them. ## At a glance - Latest release: not known (cve.now hasn't read this package's releases) - Newest unaffected release: not known without release data - Weekly downloads: 38.4M - Dependents: 31K - Registry: https://www.npmjs.com/package/socket.io-parser ## Advisories (5) ### [CVE-2026-69185](https://cve.now/CVE-2026-69185): Socket.IO: Zero-attachment Memory Exhaustion - Severity: High 7.5 - Published: Aug 3, 2026 - Affected: from 4.0.0, fixed in 4.2.7; from 3.4.0, fixed in 3.4.5; fixed in 3.3.6. ### [CVE-2026-33151](https://cve.now/CVE-2026-33151): socket.io allows an unbounded number of binary attachments - Severity: High 8.7 - Published: Mar 20, 2026 - Affected: fixed in 3.3.5; from 3.4.0, fixed in 3.4.4; from 4.0.0, fixed in 4.2.6. ### [CVE-2023-32695](https://cve.now/CVE-2023-32695): Insufficient validation when decoding a Socket.IO packet - Severity: High 7.3 - Published: May 27, 2023 - Affected: from 4.0.4, fixed in 4.2.3; from 3.4.0, fixed in 3.4.3; fixed in 3.3.4. ### [CVE-2022-2421](https://cve.now/CVE-2022-2421): Socket.io - Improper type validation in attachment parsing - Severity: Critical 10.0 - Published: Oct 25, 2022 - Affected: from 4.0.0, fixed in 4.0.5; from 4.1.0, fixed in 4.2.1; fixed in 3.3.3; from 3.4.0, fixed in 3.4.2. ### [CVE-2020-36049](https://cve.now/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… - Severity: Unrated - Published: Jan 7, 2021 - Affected: fixed in 3.3.2; from 3.4.0, fixed in 3.4.1. --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/packages/npm/socket.io-parser Site guide for agents: https://cve.now/llms.txt Uses NVD data; not endorsed by NVD.