web-token jwt-framework 1.2.0 before 3.4.10, jwt-experimental before 3.4.10, 4.0.x before 4.0.7, and 4.1.x before
Source GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.4.10 when convenient.
Data as of 21 Nov 2026, 19:14 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 3.7 |
- Patch
- Available – fixed in 3.4.10, 4.0.7, 4.1.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/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-experimental | Affected
| Fixed in
|
| web-tokenjwt-experimental | Affected
| Fixed in
|
| web-tokenjwt-experimental | 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
If you cannot patch yet, avoid using the experimental Chacha20Poly1305 key-encryption algorithm in affected versions or apply any vendor-recommended workarounds if available.
Description
A vulnerability exists in web-token jwt-framework versions before 3.4.10, jwt-experimental before 3.4.10, 4.0.x before 4.0.7, and 4.1.x before 4.1.7. The issue is a missing integrity check in the experimental Chacha20Poly1305 key-encryption algorithm, which discards the Poly1305 tag during encryption and decryption of the content encryption key. This allows attackers on the token path to modify the encrypted key without detection.
References
- github.com/web-token/jwt-framework/security/advisories/GHSA-6vvh-pxr4-25r7 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-134460 (opens in a new tab)
- vulncheck.com/advisories/web-token-jwt-framework-1.2.0-before-3.4.10-missing-authentication-in-chacha20poly1305-key-encryption (opens in a new tab)