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
Source GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 3.4.10 soon.
Data as of 21 Nov 2026, 19:14 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 21 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
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
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability is fixed in versions 3.4.10, 4.0.7, and 4.1.7 of the jwt-framework and jwt-library. Users should upgrade to these or later versions to remediate the issue. No vendor advisory or patch links were provided, so verify patch availability from the official project sources.
Description
Web-Token jwt-framework and jwt-library versions before 3.4.10, 4.0.0 before 4.0.7, and 4.1.0 before 4.1.7 have an uncontrolled resource consumption vulnerability in the PBES2AESKW::unwrapKey() function. This flaw allows unauthenticated attackers to send a JSON Web Encryption (JWE) token with a PBES2-HS*+A*KW algorithm and a very large p2c iteration count, causing excessive CPU usage due to lengthy PBKDF2 computations.