CVE-2026-25537 Vulnerability Analysis & Exploit Details

CVE-2026-25537
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-25537 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-25537 Details

Status: Analyzed

Last updated: 🕖 11 Feb 2026, 19:13 UTC
Originally published on: 🕙 04 Feb 2026, 22:15 UTC

Time between publication and last update: 6 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

CVE-2026-25537 Vulnerability Summary

CVE-2026-25537: 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.

Assessing the Risk of CVE-2026-25537

Access Complexity Graph

The exploitability of CVE-2026-25537 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-25537

With low attack complexity and no required privileges, CVE-2026-25537 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-25537, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-25537, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-25537 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2026-25537 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2026-25537 does not impact system availability.

CVE-2026-25537 References

External References

CWE Common Weakness Enumeration

CWE-843

Vulnerable Configurations

  • cpe:2.3:a:keats:jsonwebtoken:2.0.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:2.0.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:7.0.1:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:7.0.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:7.1.1:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:7.1.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:7.1.2:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:7.1.2:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:7.2.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:7.2.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:8.0.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:8.0.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:8.0.1:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:8.0.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:8.1.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:8.1.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:8.1.1:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:8.1.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:8.2.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:8.2.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:8.3.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:8.3.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:9.0.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:9.0.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:9.1.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:9.1.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:9.2.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:9.2.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:9.3.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:9.3.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:9.3.1:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:9.3.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:10.0.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:10.0.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:10.1.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:10.1.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:keats:jsonwebtoken:10.2.0:*:*:*:*:rust:*:*
    cpe:2.3:a:keats:jsonwebtoken:10.2.0:*:*:*:*:rust:*:*

Protect Your Infrastructure against CVE-2026-25537: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-2562 – A vulnerability was determined in JingDong JD Cloud Box AX6600 up to 4.5.1.r4533. This impacts the function cast_streen of the file /jdcapi of the ...
  • CVE-2026-2561 – A vulnerability was found in JingDong JD Cloud Box AX6600 up to 4.5.1.r4533. This affects the function web_get_ddns_uptime of the file /jdcapi of t...
  • CVE-2026-2447 – Heap buffer overflow in libvpx. This vulnerability affects Firefox < 147.0.4, Firefox ESR < 140.7.1, and Firefox ESR < 115.32.1.
  • CVE-2026-2032 – Malicious scripts that interrupt new tab page loading could cause desynchronization between the address bar and page content, allowing the attacker...
  • CVE-2026-2560 – A vulnerability has been found in kalcaddle kodbox up to 1.64.05. The impacted element is the function run of the file plugins/fileThumb/lib/VideoR...