Skip to main content
VulnerabilityPublished

CVE-2026-134460: web-token jwt-experimental · Missing Support for Integrity Check

Affects web-token jwt-experimentalSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.4.10 when convenient.

Data as of 21 Nov 2026, 16:45 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 20 Nov 2026.

What to do

Upgrade jwt-experimental and jwt-framework to 3.4.10; jwt-experimental and jwt-framework to 4.0.7; jwt-experimental and jwt-framework to 4.1.7.

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

AI-suggested

Upgrade to web-token jwt-framework version 3.4.10 or later, jwt-experimental version 3.4.10 or later, 4.0.x version 4.0.7 or later, or 4.1.x version 4.1.7 or later to apply the official fix that restores the integrity check in the Chacha20Poly1305 key-encryption algorithm. No other mitigation is indicated by the vendor advisory.

Description

A vulnerability in web-token jwt-framework and jwt-experimental prior to versions 3.4.10, 4.0.7, and 4.1.7 allows attackers to modify the encrypted content encryption key without detection due to a missing integrity check in the experimental Chacha20Poly1305 key-encryption algorithm. This flaw discards the Poly1305 authentication tag during encryption and omits it during decryption, weakening the cryptographic protection of the key.

References

Community reviews

Loading reviews…