CVE-2026-134461
Received Received - Intake

Uncontrolled Resource Consumption in jwt-framework and jwt-library

Vulnerability report for CVE-2026-134461, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-21

Last updated on: 2026-11-21

Assigner: VulnCheck

Description

Web-Token jwt-framework and jwt-library before 3.4.10, 4.0.0 before 4.0.7, and 4.1.0 before 4.1.7 contain an uncontrolled resource consumption vulnerability in PBES2AESKW::unwrapKey(), which passes the attacker-controlled p2c JWE header value to hash_pbkdf2() without an upper bound. Unauthenticated attackers can send a JWE using a PBES2-HS*+A*KW algorithm with a huge p2c iteration count to force lengthy PBKDF2 computations and exhaust server CPU.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-21
Last Modified
2026-11-21
Generated
2026-11-21
AI Q&A
2026-11-21
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 9 associated CPEs

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-134461 is an uncontrolled resource consumption vulnerability in the Web-Token jwt-framework and jwt-library. It affects versions before 3.4.10, 4.0.0 before 4.0.7, and 4.1.0 before 4.1.7. The issue occurs in the PBES2AESKW::unwrapKey() function where an attacker-controlled p2c JWE header value is passed to hash_pbkdf2() without an upper bound. This allows unauthenticated attackers to send a JWE using a PBES2-HS*+A*KW algorithm with a huge p2c iteration count, forcing lengthy PBKDF2 computations and exhausting server CPU.

Detection Guidance

Monitor for unusually high CPU usage on servers processing JWT tokens, particularly those using the affected jwt-framework or jwt-library versions. Check for JWE tokens with extremely high p2c values in request headers. Use network traffic analysis tools to inspect JOSE headers for PBES2-HS*+A*KW algorithms with large iteration counts.

Impact Analysis

This vulnerability can lead to denial-of-service conditions by consuming excessive server CPU resources. Attackers can send specially crafted JWE tokens with high p2c values, causing prolonged PBKDF2 computations. This may result in service unavailability, degraded performance, or system crashes for affected applications using vulnerable versions of the jwt-framework or jwt-library.

Compliance Impact

This vulnerability could lead to denial-of-service conditions by exhausting server CPU resources, potentially disrupting services handling sensitive data. For GDPR, this may impact availability of personal data processing systems, while for HIPAA, it could affect the integrity and availability of protected health information systems.

Mitigation Strategies

Upgrade to patched versions: jwt-framework >= 3.4.10, 4.0.7, or 4.1.7. If upgrading is not immediately possible, implement custom validation to enforce a maximum p2c iteration count (e.g., 1,000,000) before processing. Block or rate-limit requests with suspicious JWE headers containing high p2c values.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-134461. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...