npm package
socket.io-parser 3.1.0 vulnerabilities, and the version that fixes all of them
socket.io-parser 3.1.0 has 5 known vulnerabilities (4 rated high or critical); 3.3.6 fixes all of them.
npm (opens in a new tab) describes it as “socket.io protocol parser”
- Known vulnerabilities
- 5
- 4 rated high or critical
- Released
- Apr 24, 2017
- Latest is 4.2.7
- Downloads last week
- 25
- Under 1% of socket.io-parser downloads
- Licence
- MIT
- Pulls in
- 5 packages
- Resolved by deps.dev
What to upgrade to
3.3.6 is the closest release with no known vulnerabilities.
3.3.6Upgrade to this
Fixes all 5 known vulnerabilities. Released Jul 16, 2026.
No known vulnerabilitiesNewest 3.x release. Released Jul 15, 2026.
No known vulnerabilitiesLatest release. Released Jul 15, 2026.
No known vulnerabilities
3.3.6 came out on Jul 16, 2026. A coding agent trained before then doesn’t know it exists, so it may suggest an older release. AI knowledge cutoff dates
Hand the fix to your coding agent
One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.
Findings
- CriticalVulnerability
5 known vulnerabilities in socket.io-parser 3.1.0
EPSS: top 15%4 rated high or critical. Most serious: CVE-2020-36049, Resource exhaustion in socket.io-parser. Upgrading to 3.3.6 fixes all of them.
- LowOutdated
socket.io-parser 3.1.0 is 1 major version behind
Latest release is 4.2.7.
- LowOpenSSF Scorecard
automattic/socket.io-parser scores 1.8/10 on OpenSSF Scorecard
Weakest checks: Not actively maintained (Maintained 0/10); Little code review (Code-Review 0/10); No security policy (Security-Policy 0/10). A low score means weaker upstream security practices, not a known vulnerability.
Every advisory for socket.io-parser 3.1.0
Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.
CriticalCVE-2020-36049 on OSV.dev (opens in a new tab)GHSA-xfhh-g9f5-x4m4EPSS: top 15%
Resource exhaustion in socket.io-parser
Fixed in 3.3.2. Published Jun 30, 2021.
CriticalCVE-2022-2421 on OSV.dev (opens in a new tab)GHSA-qm95-pgcg-qqfqEPSS: top 31%
Insufficient validation when decoding a Socket.IO packet
Fixed in 3.3.3. Published Oct 26, 2022.
WarningCVE-2023-32695 on OSV.dev (opens in a new tab)GHSA-cqmj-92xf-r6r9EPSS: top 37%
Insufficient validation when decoding a Socket.IO packet
Fixed in 3.3.4. Published May 23, 2023.
CriticalCVE-2026-69185 on OSV.dev (opens in a new tab)GHSA-2m8v-j782-fhvrEPSS: top 51%
Socket.IO: Zero-attachment Memory Exhaustion
Fixed in 3.3.6. Published Aug 3, 2026.
CriticalCVE-2026-33151 on OSV.dev (opens in a new tab)GHSA-677m-j7p3-52f9EPSS: top 51%
socket.io allows an unbounded number of binary attachments
Fixed in 3.3.5. Published Mar 18, 2026.
Who is still on a vulnerable socket.io-parser
54% of last week’s 29.7M socket.io-parser downloads went to versions with known vulnerabilities.
From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.
Is socket.io-parser the only one?
Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.
How this page is checked
StackPrism asks OSV.dev which advisories affect exactly socket.io-parser 3.1.0, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.
Last checked against npm, OSV.dev, deps.dev, CISA KEV and FIRST EPSS.