CVE-2026-25537
jsonwebtoken has Type Confusion that leads to potential authorization bypass
- State
- Published
- Severity
- 5.5 Medium
- Published
- Feb 4, 2026
- Updated
- Feb 5, 2026
- Reserved
- Feb 2, 2026
Description
jsonwebtoken is a JWT lib in rust. Prior to version 10.3.0, there is a Type Confusion vulnerability in jsonwebtoken, specifically, in its claim validation logic. When a standard claim (such as nbf or exp) is provided with an incorrect JSON type (Like a String instead of a Number), the library’s internal parsing mechanism marks the claim as “FailedToParse”. Crucially, the validation logic treats this “FailedToParse” state identically to “NotPresent”. This means that if a check is enabled (like: validate_nbf = true), but the claim is not explicitly marked as required in required_spec_claims, the library will skip the validation check entirely for the malformed claim, treating it as if it were not there. This allows attackers to bypass critical time-based security restrictions (like “Not Before” checks) and commit potential authentication and authorization bypasses. This issue has been patched in version 10.3.0.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 4.0 | 5.5 Medium | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P | GitHub_M |
Weaknesses
- CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')
Affected Products
| Product | Versions |
|---|---|
jsonwebtokenKeats |
|
References
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.