VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

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

socket.io-client is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all socket.io-client vulnerabilities

Vulert verdict on socket.io-client 4.8.4 i

Updated on 23 Oct 2026

Good news: 4.8.4, the version you would install today, has no known vulnerabilities.

Package health score 91/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 4.8.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 17,433 packages i
  • Stars 63,218 i
  • OpenSSF scorecard 5/10 i
  • Last release this month 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-client, 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
4.8.4 25 Sep 2026 none MIT — Details →
4.8.3 23 Dec 2025 none MIT — Details →
4.8.2 22 Dec 2025 none MIT — Details →
4.8.1 25 Oct 2024 none MIT — Details →
4.8.0 21 Sep 2024 none MIT — Details →
4.7.5 14 Mar 2024 none MIT — Details →
4.7.4 12 Jan 2024 none MIT — Details →
4.7.3 03 Jan 2024 none MIT — Details →
4.7.2 02 Aug 2023 none MIT — Details →
4.7.1 28 Jun 2023 none MIT — Details →
4.7.0 22 Jun 2023 none MIT — Details →
4.6.2 31 May 2023 none MIT — Details →
4.6.1 20 Feb 2023 none MIT — Details →
4.6.0 06 Feb 2023 none MIT — Details →
4.6.0-alpha2 04 Feb 2023 none MIT — Details →
4.6.0-alpha1 03 Feb 2023 none MIT — Details →
4.5.4 22 Nov 2022 none MIT — Details →
4.5.3 15 Oct 2022 none MIT — Details →
4.5.2 02 Sep 2022 none MIT — Details →
2.5.0 26 Jun 2022 none MIT — Details →
4.5.1 17 May 2022 none MIT — Details →
4.5.0 23 Apr 2022 none MIT — Details →
4.4.1 06 Jan 2022 none MIT — Details →
4.4.0 18 Nov 2021 none MIT — Details →
4.3.2 16 Oct 2021 none MIT — Details →
4.3.1 15 Oct 2021 none MIT — Details →
4.3.0 14 Oct 2021 none MIT — Details →
4.2.0 30 Aug 2021 none MIT — Details →
4.1.3 10 Jul 2021 none MIT — Details →
4.1.2 17 May 2021 none MIT — Details →
4.1.1 11 May 2021 none MIT — Details →
4.1.0 11 May 2021 none MIT — Details →
4.0.2 06 May 2021 none MIT — Details →
4.0.1 31 Mar 2021 none MIT — Details →
3.1.3 12 Mar 2021 none MIT — Details →
4.0.0 10 Mar 2021 none MIT — Details →
3.1.2 26 Feb 2021 none MIT — Details →
3.1.1 03 Feb 2021 none MIT — Details →
3.1.0 15 Jan 2021 none MIT — Details →
3.0.5 05 Jan 2021 none MIT — Details →
2.4.0 04 Jan 2021 none MIT — Details →
3.0.4 07 Dec 2020 none MIT — Details →
3.0.3 19 Nov 2020 none MIT — Details →
3.0.2 17 Nov 2020 none MIT — Details →
3.0.1 09 Nov 2020 none MIT — Details →
3.0.0 05 Nov 2020 none MIT — Details →
3.0.0-rc4 30 Oct 2020 none MIT — Details →
3.0.0-rc3 26 Oct 2020 none MIT — Details →
3.0.0-rc2 15 Oct 2020 none MIT — Details →
3.0.0-rc1 13 Oct 2020 none MIT — Details →
2.3.1 30 Sep 2020 none MIT — Details →
2.3.0 20 Sep 2019 none MIT — Details →
2.2.0 28 Nov 2018 none MIT — Details →
2.1.1 17 May 2018 none MIT — Details →
2.1.0 29 Mar 2018 none MIT — Details →
2.0.4 22 Oct 2017 none MIT — Details →
2.0.3 12 Jun 2017 none MIT — Details →
2.0.2 01 Jun 2017 none MIT — Details →
2.0.1 08 May 2017 none MIT — Details →
2.0.0 08 May 2017 none MIT — Details →
1.7.4 07 May 2017 none MIT — Details →
1.7.3 17 Feb 2017 none MIT — Details →
1.7.2 11 Dec 2016 none MIT — Details →
1.7.1 27 Nov 2016 none MIT — Details →
1.7.0 27 Nov 2016 none MIT — Details →
1.6.0 20 Nov 2016 none MIT — Details →
1.5.1 24 Oct 2016 none MIT — Details →
1.5.0 06 Oct 2016 none MIT — Details →
1.4.8 24 Jun 2016 none MIT — Details →
1.4.7 24 Jun 2016 none MIT — Details →
1.4.6 03 May 2016 none MIT — Details →
1.4.5 26 Jan 2016 none MIT — Details →
1.4.4 11 Jan 2016 none MIT — Details →
1.4.3 08 Jan 2016 none MIT — Details →
1.4.2 08 Jan 2016 none MIT — Details →
1.4.1 07 Jan 2016 none MIT — Details →
1.4.0 05 Jan 2016 none MIT — Details →
1.3.7 21 Sep 2015 none MIT — Details →
1.3.6 15 Jul 2015 none MIT — Details →
1.3.5 03 Mar 2015 none MIT — Details →
1.3.4 14 Feb 2015 none MIT — Details →
1.3.3 04 Feb 2015 none MIT — Details →
1.3.2 19 Jan 2015 none MIT — Details →
1.3.1 19 Jan 2015 none MIT — Details →
1.3.0 19 Jan 2015 none MIT — Details →
1.2.1 21 Nov 2014 none MIT — Details →
1.2.0 27 Oct 2014 none MIT — Details →
1.1.0 04 Sep 2014 none MIT — Details →
1.0.6 19 Jun 2014 none MIT — Details →
1.0.5 18 Jun 2014 none MIT — Details →
1.0.4 03 Jun 2014 none MIT — Details →
1.0.3 01 Jun 2014 none MIT — Details →
1.0.2 28 May 2014 none MIT — Details →
1.0.1 28 May 2014 none MIT — Details →
0.9.17 22 May 2014 none MIT — Details →
1.0.0-pre5 22 May 2014 none MIT — Details →
1.0.0-pre4 19 May 2014 none MIT — Details →
1.0.0-pre3 17 May 2014 none MIT — Details →
1.0.0-pre2 28 Apr 2014 none MIT — Details →
1.0.0-pre 16 Mar 2014 none MIT — Details →
0.9.16 06 Jun 2013 none — — Details →
0.9.15 06 Jun 2013 none — — Details →
0.9.11 02 Nov 2012 none — — Details →
0.9.10 10 Aug 2012 none — — Details →
0.9.9 01 Aug 2012 none — — Details →
0.9.8 25 Jul 2012 none — — Details →
0.9.7 24 Jul 2012 none — — Details →
0.9.6 17 Apr 2012 none — — Details →
0.9.5 05 Apr 2012 none — — Details →
0.9.4 01 Apr 2012 none — — Details →
0.9.3 28 Mar 2012 none — — Details →
0.9.2 13 Mar 2012 none — — Details →
0.9.1-1 02 Mar 2012 none — — Details →
0.9.1 02 Mar 2012 none — — Details →
0.9.0 26 Feb 2012 none — — Details →
0.8.7 05 Nov 2011 none — — Details →
0.8.6 27 Oct 2011 none — — Details →
0.8.5 07 Oct 2011 none — — Details →
0.8.4 06 Sep 2011 none — — Details →
0.8.3 03 Sep 2011 none — — Details →

The newest 120 of 132 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for socket.io-client

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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-client

Is socket.io-client safe to use?

Vulert has no vulnerabilities on record for socket.io-client in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

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

Vulert scores socket.io-client 91/100, which reads as healthy. 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-client affected?

No. 4.8.4, 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-client should I use?

4.8.4 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-client have?

0 vulnerabilities are recorded for socket.io-client in the npm ecosystem: 0 critical, 0 high, 0 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-client vulnerabilities disclosed?

0 vulnerabilities were recorded for socket.io-client in the last 12 months. 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-client 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-client for upcoming vulnerabilities?

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