StackPrism

npm package

ws 0.8.0 vulnerabilities, and the version that fixes all of them

ws 0.8.0 has 3 known vulnerabilities (2 rated high or critical); 1.1.5 fixes all of them. 1.1.5 has 1 known vulnerability of its own, so upgrade to 8.22.0, which has none.

npm (opens in a new tab) describes it as “Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js”

Known vulnerabilities
3
2 rated high or critical
Released
Aug 21, 2015
Latest is 8.22.0
Downloads last week
3.1K
Under 1% of ws downloads
Licence
MIT
OpenSSF Scorecard
5.5/10
websockets/ws (opens in a new tab)
Pulls in
7 packages
Resolved by deps.dev

What to upgrade to

8.22.0 is the closest release with no known vulnerabilities that we checked.

  • 0.8.1

    Newest 0.8.x release. Released Nov 29, 2015.

    3 known vulnerabilities, worst rated warning

  • 1.1.5

    Fixes all 3 known vulnerabilities. Released Nov 8, 2017.

    1 known vulnerability, worst rated warning

  • 8.22.0Upgrade to this

    Latest release. Released Sep 26, 2026.

    No known vulnerabilities

8.22.0 came out on Sep 26, 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

Every advisory for ws 0.8.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.

  1. CriticalCVE-2016-10542 on OSV.dev (opens in a new tab)GHSA-6663-c963-2gqgEPSS: top 6%

    DoS due to excessively large websocket message in ws

    Fixed in 1.1.1. Published Feb 18, 2019.

  2. LowCVE-2016-10518 on OSV.dev (opens in a new tab)GHSA-2mhh-w6q8-5hxwEPSS: top 20%

    Remote Memory Disclosure in ws

    Fixed in 1.0.1. Published Feb 18, 2019.

  3. CriticalGHSA-5v72-xg48-5rpm on OSV.dev (opens in a new tab)

    Denial of Service in ws

    Fixed in 1.1.5. Published Jun 4, 2019.

Who is still on a vulnerable ws

31% of last week’s 172.6M ws 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 ws 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.

Check your whole repo

How this page is checked

StackPrism asks OSV.dev which advisories affect exactly ws 0.8.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.