CVE-2026-134461: web-token jwt-library · Unthrottled Resource Allocation
Affects web-token jwt-librarySource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 3.4.10 soon.
Data as of 21 Nov 2026, 16:44 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.7 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.5 |
- Patch
- Available – fixed in 3.4.10, 4.0.7, 4.1.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade jwt-library and jwt-framework to 3.4.10; jwt-library and jwt-framework to 4.0.7; jwt-library and jwt-framework to 4.1.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| web-tokenjwt-library | Affected
| Fixed in
|
| web-tokenjwt-library | Affected
| Fixed in
|
| web-tokenjwt-library | Affected
| Fixed in
|
| web-tokenjwt-framework | Affected
| Fixed in
|
| web-tokenjwt-framework | Affected
| Fixed in
|
| web-tokenjwt-framework | Affected
| Fixed in
|
AI-suggested
This vulnerability is fixed in versions 3.4.10, 4.0.7, and 4.1.7 of the web-token jwt-library. Users should upgrade to these or later versions to remediate the issue. No additional mitigation is required once the library is updated.
Description
CVE-2026-134461 is a high-severity vulnerability in the web-token jwt-library affecting versions before 3.4.10, 4.0.7, and 4.1.7. It involves uncontrolled resource consumption in the PBES2AESKW::unwrapKey() function, where an attacker can specify an excessively large iteration count in the p2c JWE header, causing lengthy PBKDF2 computations that exhaust server CPU resources. This vulnerability allows unauthenticated attackers to perform denial-of-service attacks by sending specially crafted JSON Web Encryption (JWE) tokens.