VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

socket.io-parser: vulnerability history, versions and safety

socket.io-parser is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 52 releases, from Jun 2021 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C1 H3 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 03 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all socket.io-parser vulnerabilities

Vulert verdict on socket.io-parser 4.2.7 i

Updated on 23 Oct 2026

Good news: 4.2.7, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 82/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 4.2.7 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.2.7 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.2.7 — unaffected i
  • Vulnerabilities on record 5 over 5 years · 2 in the last year i
  • Latest disclosure 03 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 30,922 packages i
  • Stars 63,218 i
  • OpenSSF scorecard 5/10 i
  • Last release 3 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for socket.io-parser, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.3.6 16 Jul 2026 none MIT — Details →
3.4.5 15 Jul 2026 none MIT — Details →
4.2.7 15 Jul 2026 none MIT — Details →
3.3.5 17 Mar 2026 none MIT — Details →
3.4.4 17 Mar 2026 none MIT — Details →
4.2.6 17 Mar 2026 H1 MIT Yes Details →
4.2.5 23 Dec 2025 H1 MIT Yes Details →
3.3.4 22 Jul 2024 H1 MIT Yes Details →
4.2.4 31 May 2023 H1 MIT Yes Details →
3.4.3 22 May 2023 none MIT — Details →
4.2.3 22 May 2023 H1 MIT Yes Details →
4.2.2 19 Jan 2023 H1 M1 MIT Yes Details →
3.3.3 09 Nov 2022 H1 MIT Yes Details →
3.4.2 09 Nov 2022 none MIT — Details →
4.0.5 27 Jun 2022 H1 M1 MIT Yes Details →
4.2.1 27 Jun 2022 H1 M1 MIT Yes Details →
4.2.0 17 Apr 2022 H1 M1 MIT Yes Details →
4.1.2 17 Feb 2022 H1 M1 MIT Yes Details →
4.1.1 14 Oct 2021 H1 M1 MIT Yes Details →
4.1.0 11 Oct 2021 H1 M1 MIT Yes Details →
4.0.4 15 Jan 2021 C1 H1 M1 MIT Yes Details →
3.3.2 09 Jan 2021 H1 MIT Yes Details →
4.0.3 05 Jan 2021 C1 H1 MIT Yes Details →
4.0.2 25 Nov 2020 C1 H1 MIT Yes Details →
4.0.1 05 Nov 2020 C1 H1 MIT Yes Details →
4.0.1-rc3 25 Oct 2020 C1 H1 MIT Yes Details →
4.0.1-rc2 15 Oct 2020 C1 H1 MIT Yes Details →
4.0.1-rc1 12 Oct 2020 C1 H1 MIT Yes Details →
3.3.1 30 Sep 2020 H2 MIT Yes Details →
4.0.0 28 Sep 2020 C1 H1 MIT Yes Details →
3.4.1 13 May 2020 none MIT — Details →
3.4.0 20 Sep 2019 none MIT — Details →
3.3.0 07 Nov 2018 H2 MIT Yes Details →
3.2.0 28 Feb 2018 H2 MIT Yes Details →
3.1.3 25 Feb 2018 H2 MIT Yes Details →
3.1.2 27 Apr 2017 H2 MIT Yes Details →
3.1.1 24 Apr 2017 H2 MIT Yes Details →
3.1.0 24 Apr 2017 H2 MIT Yes Details →
3.0.0 03 Apr 2017 H2 MIT Yes Details →
2.3.2 30 Dec 2016 H2 MIT Yes Details →
2.3.1 24 Oct 2016 H2 MIT Yes Details →
2.3.0 20 Oct 2016 H2 MIT Yes Details →
2.2.6 25 Nov 2015 H2 MIT Yes Details →
2.2.5 21 Nov 2015 H2 MIT Yes Details →
2.2.4 03 Mar 2015 H2 MIT Yes Details →
2.2.3 04 Feb 2015 H2 MIT Yes Details →
2.2.2 04 Sep 2014 H2 MIT Yes Details →
2.2.1 20 Jun 2014 H2 MIT Yes Details →
2.2.0 31 May 2014 H2 MIT Yes Details →
2.1.5 24 May 2014 H2 MIT Yes Details →
2.1.4 17 May 2014 H2 MIT Yes Details →
2.1.3 28 Apr 2014 H2 MIT Yes Details →
2.1.2 06 Mar 2014 H2 MIT Yes Details →
2.1.1 05 Mar 2014 H2 MIT Yes Details →
2.1.0 01 Mar 2014 H2 MIT Yes Details →
2.0.0 20 Feb 2014 H2 MIT Yes Details →
1.1.2 11 Feb 2014 H2 MIT Yes Details →
1.1.1 11 Feb 2014 H2 MIT Yes Details →
1.1.0 25 Dec 2013 H2 MIT Yes Details →
1.0.2 18 Dec 2012 H2 MIT Yes Details →
1.0.1 10 Dec 2012 H2 MIT Yes Details →

All 61 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1
  • 2023 1
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for socket.io-parser

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2022-2421: Insufficient validation when decoding a Socket.IO packet in socket.io-parser 9.8 critical 4.0.5 26 Oct 2022
CVE-2026-33151: socket.io Allows Unbounded Number of Binary Attachments Leading to Memory Exhaustion 8.7 high 3.3.5 18 Mar 2026
CVE-2020-36049: Resource Exhaustion in socket.io-parser 7.5 high 3.3.2 30 Jun 2021
CVE-2026-69185: Socket.IO Zero-Attachment Memory Exhaustion Vulnerability 7.5 high 4.2.7 03 Aug 2026
CVE-2023-32695: Insufficient validation when decoding a Socket.IO packet in socket.io-parser 7.3 medium 4.2.3 23 May 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About socket.io-parser

Is socket.io-parser safe to use?

Vulert records 5 vulnerabilities for socket.io-parser in npm: 1 critical, 3 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is socket.io-parser's Vulert package health score?

Vulert scores socket.io-parser 82/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of socket.io-parser affected?

No. 4.2.7, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of socket.io-parser should I use?

4.2.7 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does socket.io-parser have?

5 vulnerabilities are recorded for socket.io-parser in the npm ecosystem: 1 critical, 3 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new socket.io-parser vulnerabilities disclosed?

2 vulnerabilities were recorded for socket.io-parser in the last 12 months, and the oldest entry in this database dates to 30 Jun 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of socket.io-parser are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor socket.io-parser for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the socket.io-parser version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.