VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

jsonwebtoken: vulnerability history, versions and safety

jsonwebtoken is a package in the crates.io ecosystem. Vulert records 1 vulnerability for it across 55 releases, first recorded in Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
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 03 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jsonwebtoken vulnerabilities

Vulert verdict on jsonwebtoken 11.1.0 i

Updated on 23 Oct 2026

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

Package health score 74/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 11.1.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 03 Feb 2026 i
  • Highest CVSS 5.5 i
  • With no published fix 0 i
  • Stars 2,102 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by crates.io, 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 jsonwebtoken, 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
11.1.0 16 Sep 2026 none MIT — Details →
11.0.0 24 Jul 2026 none MIT — Details →
10.4.0 11 May 2026 none MIT — Details →
10.3.0 27 Jan 2026 none MIT — Details →
10.2.0 06 Nov 2025 M1 MIT Yes Details →
10.1.0 18 Oct 2025 M1 MIT Yes Details →
10.0.0 29 Sep 2025 M1 MIT Yes Details →
9.3.1 06 Feb 2025 M1 MIT Yes Details →
9.3.0 21 Mar 2024 M1 MIT Yes Details →
9.2.0 01 Dec 2023 M1 MIT Yes Details →
9.1.0 21 Oct 2023 M1 MIT Yes Details →
9.0.0 16 Oct 2023 M1 MIT Yes Details →
8.3.0 15 Mar 2023 M1 MIT Yes Details →
8.2.0 03 Dec 2022 M1 MIT Yes Details →
8.1.1 17 Jun 2022 M1 MIT Yes Details →
8.1.0 12 Apr 2022 M1 MIT Yes Details →
8.0.1 03 Feb 2022 M1 MIT Yes Details →
8.0.0 02 Feb 2022 M1 MIT Yes Details →
8.0.0-beta.8 28 Jan 2022 M1 MIT Yes Details →
8.0.0-beta.7 16 Dec 2021 M1 MIT Yes Details →
8.0.0-beta.6 19 Nov 2021 M1 MIT Yes Details →
8.0.0-beta.5 01 Nov 2021 M1 MIT Yes Details →
8.0.0-beta.4 10 Oct 2021 M1 MIT Yes Details →
8.0.0-beta.3 28 Sep 2021 M1 MIT Yes Details →
8.0.0-beta.2 22 Mar 2021 M1 MIT Yes Details →
8.0.0-beta.1 25 Feb 2021 M1 MIT Yes Details →
8.0.0-beta.0 20 Feb 2021 M1 MIT Yes Details →
7.2.0 30 Jun 2020 M1 MIT Yes Details →
7.1.2 16 Jun 2020 M1 MIT Yes Details →
7.1.1 09 Jun 2020 M1 MIT Yes Details →
7.1.0 01 Mar 2020 M1 MIT Yes Details →
7.0.1 31 Jan 2020 M1 MIT Yes Details →
7.0.0 29 Jan 2020 M1 MIT Yes Details →
7.0.0-beta.1 21 Jan 2020 M1 MIT Yes Details →
7.0.0-alpha.2 28 Nov 2019 M1 MIT Yes Details →
7.0.0-alpha.1 15 Nov 2019 M1 MIT Yes Details →
6.0.1 10 May 2019 M1 MIT Yes Details →
6.0.0 21 Apr 2019 M1 MIT Yes Details →
5.0.1 10 Sep 2018 M1 MIT Yes Details →
5.0.0 13 Aug 2018 M1 MIT Yes Details →
4.0.1 19 Mar 2018 M1 MIT Yes Details →
4.0.0 22 Nov 2017 M1 MIT Yes Details →
3.0.0 08 Sep 2017 M1 MIT Yes Details →
2.0.3 18 Jul 2017 M1 MIT Yes Details →
2.0.2 24 Jun 2017 M1 MIT Yes Details →
2.0.1 09 May 2017 M1 MIT Yes Details →
2.0.0 23 Apr 2017 M1 MIT Yes Details →
2.0.0-beta-1 20 Apr 2017 M1 MIT Yes Details →
1.1.7 02 Apr 2017 M1 MIT Yes Details →
1.1.6 13 Feb 2017 M1 MIT Yes Details →
1.1.5 24 Aug 2016 M1 MIT Yes Details →
1.1.4 23 Aug 2016 M1 MIT Yes Details →
1.1.3 25 Apr 2016 M1 MIT Yes Details →
1.1.2 11 Apr 2016 M1 MIT Yes Details →
1.1.1 29 Mar 2016 M1 MIT Yes Details →
1.1.0 29 Feb 2016 M1 MIT Yes Details →
1.0.0 22 Dec 2015 M1 MIT Yes Details →
0.2.0 08 Nov 2015 M1 MIT Yes Details →
0.1.0 02 Nov 2015 M1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for jsonwebtoken

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Type Confusion Vulnerability in jsonwebtoken: Potential Authorization Bypass 5.5 medium 10.3.0 03 Feb 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: 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 jsonwebtoken

Is jsonwebtoken safe to use?

Vulert records 1 vulnerabilities for jsonwebtoken in crates.io: 0 critical, 0 high, 1 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 jsonwebtoken's Vulert package health score?

Vulert scores jsonwebtoken 74/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 jsonwebtoken affected?

No. 11.1.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 jsonwebtoken should I use?

11.1.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 jsonwebtoken have?

1 vulnerability is recorded for jsonwebtoken in the crates.io ecosystem: 0 critical, 0 high, 1 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 jsonwebtoken vulnerabilities disclosed?

1 vulnerability was recorded for jsonwebtoken in the last 12 months, and the oldest entry in this database dates to 03 Feb 2026. 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 jsonwebtoken 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 jsonwebtoken for upcoming vulnerabilities?

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