Skip to main content
CVE-2026-134460VulnerabilityPublished

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

0
Compare
Authoritative record:CVE-2026-134460· Medium 6.3

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

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.3
CNA (VulnCheck)CVSS 3.13.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
web-tokenjwt-experimentalAffected
  • >=3.3.0 <3.4.10
Fixed in
  • 3.4.10
web-tokenjwt-experimentalAffected
  • >=4.0.0 <4.0.7
Fixed in
  • 4.0.7
web-tokenjwt-experimentalAffected
  • >=4.1.0 <4.1.7
Fixed in
  • 4.1.7
web-tokenjwt-frameworkAffected
  • >=1.2.0 <3.4.10
Fixed in
  • 3.4.10
web-tokenjwt-frameworkAffected
  • >=4.0.0 <4.0.7
Fixed in
  • 4.0.7
web-tokenjwt-frameworkAffected
  • >=4.1.0 <4.1.7
Fixed in
  • 4.1.7

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

Community reviews

Loading reviews…