VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

fast-jwt: vulnerability history, versions and safety

fast-jwt is a package in the npm ecosystem. Vulert records 14 vulnerabilities for it across 72 releases, from Nov 2023 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded C4 H4 M6
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
12 in the last 12 months

Most recent disclosure 08 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all fast-jwt vulnerabilities

Vulert verdict on fast-jwt 6.3.5 i

Updated on 23 Oct 2026

Careful: 6.3.5 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 53/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.3.5 — affected i
  • Vulnerabilities on record 14 over 2 years · 12 in the last year i
  • Latest disclosure 08 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Depended on by 148 packages i
  • Stars 437 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence Apache-2.0 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 fast-jwt, 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
6.3.5 15 Oct 2026 C1 H1 Apache-2.0 No Details →
6.3.4 04 Oct 2026 C1 H1 Apache-2.0 No Details →
6.3.3 03 Sep 2026 C1 H1 M1 Apache-2.0 No Details →
6.3.2 04 Aug 2026 C1 H1 M1 Apache-2.0 No Details →
6.3.1 30 Jul 2026 C1 H1 M1 Apache-2.0 No Details →
6.3.0 28 Jul 2026 C1 H2 M1 Apache-2.0 No Details →
6.2.4 29 Apr 2026 H1 Apache-2.0 Yes Details →
6.2.3 26 Apr 2026 C3 H3 M2 Apache-2.0 No Details →
6.2.2 10 Apr 2026 C3 H3 M2 Apache-2.0 No Details →
6.2.1 09 Apr 2026 C3 H3 M2 Apache-2.0 No Details →
6.2.0 07 Apr 2026 C3 H3 M4 Apache-2.0 No Details →
6.1.0 01 Dec 2025 C2 H3 M4 Apache-2.0 No Details →
6.0.2 27 May 2025 C3 H3 M4 Apache-2.0 No Details →
6.0.1 31 Mar 2025 C3 H3 M4 Apache-2.0 No Details →
6.0.0 20 Mar 2025 C3 H3 M4 Apache-2.0 No Details →
5.0.6 19 Mar 2025 C3 H3 M4 Apache-2.0 No Details →
5.0.5 14 Jan 2025 C3 H3 M5 Apache-2.0 No Details →
5.0.2 13 Dec 2024 C3 H3 M5 Apache-2.0 No Details →
5.0.1 11 Dec 2024 C3 H3 M5 Apache-2.0 No Details →
5.0.0 20 Nov 2024 C3 H3 M5 Apache-2.0 No Details →
4.0.6 20 Nov 2024 C3 H3 M4 Apache-2.0 No Details →
4.0.5 09 Sep 2024 C3 H3 M4 Apache-2.0 No Details →
4.0.3 27 Aug 2024 C3 H3 M4 Apache-2.0 No Details →
4.0.2 15 Jul 2024 C3 H3 M4 Apache-2.0 No Details →
4.0.1 27 Apr 2024 C3 H3 M4 Apache-2.0 No Details →
4.0.0 15 Feb 2024 C3 H3 M4 Apache-2.0 No Details →
3.3.3 29 Jan 2024 C3 H3 M4 Apache-2.0 No Details →
3.3.2 20 Nov 2023 C3 H3 M4 Apache-2.0 No Details →
3.3.1 05 Oct 2023 C3 H3 M5 Apache-2.0 No Details →
3.3.0 21 Sep 2023 C3 H3 M5 Apache-2.0 No Details →
3.2.0 18 Aug 2023 C3 H3 M5 Apache-2.0 No Details →
3.1.1 08 Jun 2023 C3 H3 M5 Apache-2.0 No Details →
3.1.0 30 May 2023 C3 H3 M5 Apache-2.0 No Details →
3.0.0 19 May 2023 C3 H3 M5 Apache-2.0 No Details →
2.2.3 11 May 2023 C3 H3 M5 Apache-2.0 No Details →
2.2.2 27 Apr 2023 C3 H3 M5 Apache-2.0 No Details →
2.2.1 30 Mar 2023 C3 H3 M5 Apache-2.0 No Details →
2.2.0 07 Feb 2023 C3 H3 M5 Apache-2.0 No Details →
2.1.0 10 Jan 2023 C3 H3 M5 Apache-2.0 No Details →
2.0.2 18 Nov 2022 C3 H3 M5 Apache-2.0 No Details →
2.0.0 14 Nov 2022 C3 H3 M5 Apache-2.0 No Details →
1.7.2 13 Nov 2022 C3 H3 M5 Apache-2.0 No Details →
1.7.1 06 Sep 2022 C3 H3 M5 Apache-2.0 No Details →
1.7.0 01 Aug 2022 C3 H3 M5 Apache-2.0 No Details →
1.6.1 10 Jul 2022 C3 H3 M5 Apache-2.0 No Details →
1.6.0 21 Jun 2022 C3 H3 M5 Apache-2.0 No Details →
1.5.4 28 Apr 2022 C3 H3 M5 Apache-2.0 No Details →
1.5.3 06 Apr 2022 C3 H3 M5 Apache-2.0 No Details →
1.5.2 04 Apr 2022 C3 H3 M5 Apache-2.0 No Details →
1.5.1 21 Feb 2022 C3 H3 M5 Apache-2.0 No Details →
1.5.0 17 Feb 2022 C3 H3 M5 Apache-2.0 No Details →
1.4.1 30 Dec 2021 C3 H3 M5 Apache-2.0 No Details →
1.4.0 02 Dec 2021 C3 H3 M5 Apache-2.0 No Details →
1.3.2 10 Nov 2021 C3 H3 M5 Apache-2.0 No Details →
1.3.1 03 Nov 2021 C3 H3 M5 Apache-2.0 No Details →
1.3.0 01 Nov 2021 C3 H3 M5 Apache-2.0 No Details →
1.2.0 18 Jun 2021 C3 H3 M5 Apache-2.0 No Details →
1.1.3 11 Mar 2021 C3 H3 M5 Apache-2.0 No Details →
1.1.2 10 Mar 2021 C3 H3 M5 Apache-2.0 No Details →
1.1.1 08 Mar 2021 C3 H3 M5 Apache-2.0 No Details →
1.1.0 25 Jan 2021 C3 H3 M5 Apache-2.0 No Details →
1.0.0 21 Jan 2021 C3 H3 M5 Apache-2.0 No Details →
0.5.1 24 Oct 2020 C3 H3 M5 Apache-2.0 No Details →
0.5.0 24 Oct 2020 C3 H3 M5 Apache-2.0 No Details →
0.4.2 13 Oct 2020 C3 H3 M5 Apache-2.0 No Details →
0.4.1 09 Sep 2020 C3 H3 M5 Apache-2.0 No Details →
0.4.0 08 Sep 2020 C3 H3 M5 Apache-2.0 No Details →
0.3.1 04 Sep 2020 C3 H3 M5 Apache-2.0 No Details →
0.3.0 27 Aug 2020 C3 H3 M5 Apache-2.0 No Details →
0.2.0 17 Aug 2020 C3 H3 M5 Apache-2.0 No Details →
0.1.1 23 Jun 2020 C3 H3 M5 Apache-2.0 No Details →
0.1.0 23 Jun 2020 C3 H3 M5 Apache-2.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2025 1
  • 2026 12

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

03 Vulnerabilities

Recorded vulnerabilities for fast-jwt

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-107722: fast-jwt Incomplete Patch Enables RSA to HS256 Algorithm Confusion 9.8 critical 6.3.0 08 Oct 2026
CVE-2026-44351: fast-jwt Authentication Bypass via Empty HMAC Secret 9.1 critical 6.2.4 06 May 2026
CVE-2026-35039: fast-jwt Cache Confusion Vulnerability Leading to Identity and Authorization Issues 9.1 critical 6.1.0 03 Apr 2026
CVE-2026-34950: fast-jwt Incomplete Fix for JWT Algorithm Confusion via Whitespace-Prefixed RSA Public Key 9.1 critical No fix published 02 Apr 2026
CVE-2026-107723: fast-jwt Silent Claim-Validator Bypass Vulnerability 8.1 high 6.3.0 08 Oct 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 fast-jwt

Is fast-jwt safe to use?

Vulert records 14 vulnerabilities for fast-jwt in npm: 4 critical, 4 high, 6 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is fast-jwt's Vulert package health score?

Vulert scores fast-jwt 53/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of fast-jwt affected?

Yes. 6.3.5, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does fast-jwt have?

14 vulnerabilities are recorded for fast-jwt in the npm ecosystem: 4 critical, 4 high, 6 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 fast-jwt vulnerabilities disclosed?

12 vulnerabilities were recorded for fast-jwt in the last 12 months, and the oldest entry in this database dates to 20 Nov 2023. 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 fast-jwt 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 fast-jwt for upcoming vulnerabilities?

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