npm package
jsonwebtoken 8.1.0 vulnerabilities
OSV.dev didn’t answer just now, so we can’t say whether jsonwebtoken 8.1.0 has known vulnerabilities. This page checks again within the hour.
npm (opens in a new tab) describes it as “JSON Web Token implementation (symmetric and asymmetric)”
- Known vulnerabilities
- Not checked
- OSV.dev didn’t answer
- Released
- Oct 9, 2017
- Latest is 9.0.3
- Downloads last week
- 24.1K
- Under 1% of jsonwebtoken downloads
- Licence
- MIT
- Pulls in
- 14 packages
- Resolved by deps.dev
What to upgrade to
9.0.3 is the closest release with no known vulnerabilities that we checked.
Newest 8.x release. Released Mar 18, 2019.
3 known vulnerabilities, worst rated warning9.0.3Upgrade to this
Latest release. Released Dec 4, 2025.
No known vulnerabilities
9.0.3 came out on Dec 4, 2025. A coding agent trained before then doesn’t know it exists, so it may suggest an older release. AI knowledge cutoff dates
Findings
- LowOutdated
jsonwebtoken 8.1.0 is 1 major version behind
Latest release is 9.0.3.
Who is still on a vulnerable jsonwebtoken
6% of last week’s 60.4M jsonwebtoken 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 jsonwebtoken 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.
How this page is checked
StackPrism asks OSV.dev which advisories affect exactly jsonwebtoken 8.1.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 (didn’t answer) and deps.dev. Findings from that source may be missing; this page refreshes soon.