VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

ws: vulnerability history, versions and safety

ws is a package in the npm ecosystem. Vulert records 7 vulnerabilities for it across 83 releases, from Feb 2019 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H4 M2 L1
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 15 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ws vulnerabilities

Vulert verdict on ws 8.22.0 i

Updated on 22 Oct 2026

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

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

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

  • Current release 8.22.0 — unaffected i
  • Vulnerabilities on record 7 over 7 years · 2 in the last year i
  • Latest disclosure 15 Jun 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 177,582 packages i
  • Stars 22,807 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 ws, 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
8.22.0 26 Sep 2026 none MIT — Details →
8.21.3 07 Aug 2026 none MIT — Details →
8.21.2 03 Aug 2026 none MIT — Details →
7.5.13 17 Jul 2026 none MIT — Details →
6.2.6 17 Jul 2026 none MIT — Details →
5.2.7 17 Jul 2026 none MIT — Details →
8.21.1 14 Jul 2026 none MIT — Details →
7.5.12 14 Jul 2026 none MIT — Details →
6.2.5 14 Jul 2026 none MIT — Details →
5.2.6 14 Jul 2026 none MIT — Details →
8.21.0 22 May 2026 none MIT — Details →
7.5.11 22 May 2026 none MIT — Details →
6.2.4 22 May 2026 none MIT — Details →
5.2.5 22 May 2026 none MIT — Details →
8.20.1 12 May 2026 none MIT — Details →
8.20.0 21 Mar 2026 M1 MIT Yes Details →
8.19.0 05 Jan 2026 M1 MIT Yes Details →
8.18.3 28 Jun 2025 M1 MIT Yes Details →
8.18.2 03 May 2025 M1 MIT Yes Details →
8.18.1 21 Feb 2025 M1 MIT Yes Details →
8.18.0 03 Jul 2024 M1 MIT Yes Details →
8.17.1 16 Jun 2024 M1 MIT Yes Details →
7.5.10 16 Jun 2024 none MIT — Details →
6.2.3 16 Jun 2024 none MIT — Details →
5.2.4 16 Jun 2024 H1 MIT Yes Details →
8.17.0 28 Apr 2024 M1 MIT Yes Details →
8.16.0 26 Dec 2023 M1 MIT Yes Details →
8.15.1 12 Dec 2023 M1 MIT Yes Details →
8.15.0 09 Dec 2023 M1 MIT Yes Details →
8.14.2 19 Sep 2023 M1 MIT Yes Details →
8.14.1 08 Sep 2023 M1 MIT Yes Details →
8.14.0 06 Sep 2023 M1 MIT Yes Details →
8.13.0 10 Mar 2023 M1 MIT Yes Details →
8.12.1 13 Feb 2023 M1 MIT Yes Details →
8.12.0 07 Jan 2023 M1 MIT Yes Details →
8.11.0 06 Nov 2022 M1 MIT Yes Details →
8.10.0 24 Oct 2022 M1 MIT Yes Details →
8.9.0 22 Sep 2022 M1 MIT Yes Details →
8.8.1 15 Jul 2022 M1 MIT Yes Details →
7.5.9 15 Jul 2022 none MIT — Details →
8.8.0 09 Jun 2022 M1 MIT Yes Details →
8.7.0 26 May 2022 M1 MIT Yes Details →
7.5.8 26 May 2022 none MIT — Details →
8.6.0 01 May 2022 M1 MIT Yes Details →
8.5.0 07 Feb 2022 M1 MIT Yes Details →
7.5.7 07 Feb 2022 none MIT — Details →
8.4.2 14 Jan 2022 M1 MIT Yes Details →
8.4.1 13 Jan 2022 M1 MIT Yes Details →
8.4.0 20 Dec 2021 M1 MIT Yes Details →
7.5.6 23 Nov 2021 none MIT — Details →
8.3.0 23 Nov 2021 M1 MIT Yes Details →
8.2.3 02 Oct 2021 M1 MIT Yes Details →
8.2.2 08 Sep 2021 M1 MIT Yes Details →
7.5.5 08 Sep 2021 none MIT — Details →
8.2.1 28 Aug 2021 M1 MIT Yes Details →
7.5.4 28 Aug 2021 none MIT — Details →
8.2.0 18 Aug 2021 M1 MIT Yes Details →
8.1.0 11 Aug 2021 M1 MIT Yes Details →
8.0.0 28 Jul 2021 M1 MIT Yes Details →
7.5.3 10 Jul 2021 none MIT — Details →
7.5.2 04 Jul 2021 none MIT — Details →
7.5.1 29 Jun 2021 none MIT — Details →
7.5.0 16 Jun 2021 none MIT — Details →
5.2.3 08 Jun 2021 H2 MIT Yes Details →
6.2.2 01 Jun 2021 none MIT — Details →
7.4.6 25 May 2021 none MIT — Details →
7.4.5 18 Apr 2021 M1 MIT Yes Details →
7.4.4 06 Mar 2021 M1 MIT Yes Details →
7.4.3 02 Feb 2021 M1 MIT Yes Details →
7.4.2 29 Dec 2020 M1 MIT Yes Details →
7.4.1 04 Dec 2020 M1 MIT Yes Details →
7.4.0 08 Nov 2020 M1 MIT Yes Details →
7.3.1 05 Jul 2020 M1 MIT Yes Details →
7.3.0 10 May 2020 M1 MIT Yes Details →
7.2.5 25 Apr 2020 M1 MIT Yes Details →
7.2.3 09 Mar 2020 M1 MIT Yes Details →
7.2.2 08 Mar 2020 M1 MIT Yes Details →
7.2.1 14 Dec 2019 M1 MIT Yes Details →
7.2.0 19 Oct 2019 M1 MIT Yes Details →
7.1.2 12 Aug 2019 M1 MIT Yes Details →
7.1.1 19 Jul 2019 M1 MIT Yes Details →
7.1.0 08 Jul 2019 M1 MIT Yes Details →
7.0.1 17 Jun 2019 M1 MIT Yes Details →
7.0.0 30 Apr 2019 M1 MIT Yes Details →
6.2.1 27 Mar 2019 none MIT — Details →
6.2.0 06 Mar 2019 none MIT — Details →
6.1.4 16 Feb 2019 none MIT — Details →
6.1.3 24 Jan 2019 none MIT — Details →
6.1.2 17 Nov 2018 none MIT — Details →
6.1.1 17 Nov 2018 none MIT — Details →
6.1.0 05 Oct 2018 none MIT — Details →
6.0.0 21 Jul 2018 none MIT — Details →
5.2.2 11 Jul 2018 H2 MIT Yes Details →
5.2.1 23 Jun 2018 H2 MIT Yes Details →
5.2.0 21 May 2018 H2 MIT Yes Details →
5.1.1 02 Apr 2018 H2 MIT Yes Details →
5.1.0 19 Mar 2018 H2 MIT Yes Details →
5.0.0 06 Mar 2018 H2 MIT Yes Details →
4.1.0 22 Feb 2018 H2 MIT Yes Details →
4.0.0 05 Jan 2018 H2 MIT Yes Details →
3.3.3 17 Dec 2017 H2 — Yes Details →
3.3.2 21 Nov 2017 H2 — Yes Details →
3.3.1 08 Nov 2017 H2 — Yes Details →
1.1.5 08 Nov 2017 H1 — Yes Details →
3.3.0 04 Nov 2017 H2 — Yes Details →
3.2.0 15 Sep 2017 H2 — Yes Details →
3.1.0 27 Jul 2017 H2 — Yes Details →
3.0.0 17 May 2017 H2 — Yes Details →
2.3.1 20 Apr 2017 H2 — Yes Details →
2.3.0 20 Apr 2017 H2 — Yes Details →
2.2.3 03 Apr 2017 H2 — Yes Details →
2.2.2 21 Mar 2017 H2 — Yes Details →
2.2.1 13 Mar 2017 H2 — Yes Details →
1.1.4 11 Mar 2017 H2 — Yes Details →
1.1.3 11 Mar 2017 H2 — Yes Details →
2.2.0 28 Feb 2017 H2 — Yes Details →
2.1.0 18 Feb 2017 H2 — Yes Details →
1.1.2 13 Feb 2017 H2 — Yes Details →
2.0.3 08 Feb 2017 H1 — Yes Details →
2.0.2 03 Feb 2017 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 3
  • 2021 1
  • 2024 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for ws

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service in ws 7.5 high 1.1.5 04 Jun 2019
CVE-2024-37890: Denial of Service in ws Package 7.5 high 5.2.4 17 Jun 2024
CVE-2026-48779: ws Package Memory Exhaustion DoS from Tiny Fragments and Data Chunks 7.5 high 5.2.5 15 Jun 2026
CVE-2021-32640: ReDoS in Sec-Websocket-Protocol header in ws 5.3 medium 7.4.6 28 May 2021
CVE-2026-45736: ws Package Uninitialized Memory Disclosure Vulnerability 4.4 medium 8.20.1 18 May 2026

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 ws

Is ws safe to use?

Vulert records 7 vulnerabilities for ws in npm: 0 critical, 4 high, 2 medium and 1 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 ws's Vulert package health score?

Vulert scores ws 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 ws affected?

No. 8.22.0, 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 ws should I use?

8.22.0 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 ws have?

7 vulnerabilities are recorded for ws in the npm ecosystem: 0 critical, 4 high, 2 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ws vulnerabilities disclosed?

2 vulnerabilities were recorded for ws in the last 12 months, and the oldest entry in this database dates to 18 Feb 2019. 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 ws 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 ws for upcoming vulnerabilities?

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