Access of Resource Using Incompatible Type ('Type Confusion') Affecting rust-jsonwebtoken package, versions *


Severity

Recommended
low

Based on Debian security rating.

Threat Intelligence

EPSS
0.5% (43rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN13-RUSTJSONWEBTOKEN-15234895
  • published6 Feb 2026
  • disclosed4 Feb 2026

Introduced: 4 Feb 2026

CVE-2026-25537  (opens in a new tab)
CWE-843  (opens in a new tab)

How to fix?

There is no fixed version for Debian:13 rust-jsonwebtoken.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-jsonwebtoken package and not the rust-jsonwebtoken package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1