VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

jws: vulnerability history, versions and safety

jws is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 22 releases, from Sep 2020 to Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 04 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jws vulnerabilities

Vulert verdict on jws 4.0.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 4.0.1 — unaffected i
  • Vulnerabilities on record 2 over 5 years · 1 in the last year i
  • Latest disclosure 04 Dec 2025 i
  • Highest CVSS 8.7 i
  • With no published fix 0 i
  • Depended on by 87,522 packages i
  • Stars 721 i
  • OpenSSF scorecard 4/10 i
  • Last release 10 months ago i
  • Licence MIT i
  • Similar names ws 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 jws, 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.0.1 04 Dec 2025 none MIT — Details →
3.2.3 04 Dec 2025 none MIT — Details →
4.0.0 16 Dec 2019 none MIT — Details →
3.2.2 16 Mar 2019 H1 MIT Yes Details →
3.2.1 27 Jan 2019 H1 MIT Yes Details →
3.2.0 25 Jan 2019 H1 MIT Yes Details →
3.1.5 14 May 2018 H1 MIT Yes Details →
3.1.4 03 Nov 2016 H1 MIT Yes Details →
3.1.3 18 Feb 2016 H1 MIT Yes Details →
3.1.2 18 Feb 2016 H1 MIT Yes Details →
3.1.1 17 Jan 2016 H1 MIT Yes Details →
3.1.0 16 Jul 2015 H1 MIT Yes Details →
3.0.0 08 Apr 2015 H1 MIT Yes Details →
2.0.0 30 Jan 2015 H2 MIT Yes Details →
1.0.1 11 Jan 2015 H2 MIT Yes Details →
1.0.0 07 Dec 2014 H2 MIT Yes Details →
0.2.6 07 Aug 2014 H2 MIT Yes Details →
0.2.5 30 Jan 2014 H2 MIT Yes Details →
0.2.4 28 Jan 2014 H2 MIT Yes Details →
0.2.3 06 Nov 2013 H2 MIT Yes Details →
0.2.2 12 Mar 2013 H2 MIT Yes Details →
0.2.1 25 Feb 2013 H2 MIT Yes Details →
0.2.0 10 Feb 2013 H2 MIT Yes Details →
0.0.2 18 Jan 2013 H2 MIT Yes Details →
0.0.1 16 Jan 2013 H2 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for jws

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2016-1000223: Forgeable Public/Private Tokens in jws 8.7 high 3.0.0 01 Sep 2020
CVE-2025-65945: auth0/node-jws Improper HMAC Signature Verification Vulnerability 7.5 high 3.2.3 04 Dec 2025

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 jws

Is jws safe to use?

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

Vulert scores jws 78/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 jws affected?

No. 4.0.1, 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 jws should I use?

4.0.1 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 jws have?

2 vulnerabilities are recorded for jws in the npm ecosystem: 0 critical, 2 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 jws vulnerabilities disclosed?

1 vulnerability was recorded for jws in the last 12 months, and the oldest entry in this database dates to 01 Sep 2020. 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 jws 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 jws for upcoming vulnerabilities?

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