CVE-2026-25537 PUBLISHED

jsonwebtoken has Type Confusion that leads to potential authorization bypass

Assigner: GitHub_M
Reserved: 02.02.2026 Published: 04.02.2026 Updated: 04.02.2026

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.

Metrics

CVSS Vector: 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
CVSS Score: 5.5

Product Status

Vendor Keats
Product jsonwebtoken
Versions
  • Version < 10.3.0 is affected

References

Problem Types

  • CWE-843: Access of Resource Using Incompatible Type ('Type Confusion') CWE