Jsonwebtoken
5 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Jsonwebtoken, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Jsonwebtoken CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 1 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 5 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- Critical1
- High1
- Medium3
Latest CVEs
The 5 most recently published vulnerabilities affecting Jsonwebtoken.
- CVE-2026-25537jsonwebtoken has Type Confusion that leads to potential authorization bypass7.5
- CVE-2022-23539jsonwebtoken unrestricted key type could lead to legacy keys usage5.9
- CVE-2022-23540jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()6.4
- CVE-2022-23541jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC5.0
- CVE-2015-9235In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the atta...9.8
Product grouping is registry-driven, with AI assist and human review. How it works