cve.bz

CVE-2026-134460 web-token jwt-framework 1.2.0 before 3.4.10 Missing Authentication in Chacha20Poly1305 Key Encryption

6.3 mediumFix available

Medium (6.3) in web-token. Fixed in web-token/jwt-library 3.4.10, 4.0.7, 4.1.7.

On this page
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 4.1.7 contain a missing integrity check in the experimental Chacha20Poly1305 key-encryption algorithm, which discards the Poly1305 tag in encryptKey() and calls openssl_decrypt() without it in decryptKey(). Attackers on the token path can modify the encrypted content encryption key undetected.

Severity

CVSS 4.0

6.3 medium
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

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
CWE
CWE-353 Missing Support for Integrity Check
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Assigned by
VulnCheck (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • web-token/jwt-library (Packagist): fixed in 3.4.10, 4.0.7, 4.1.7

Ask an AI about this CVE

Show the promptExplain CVE-2026-134460 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-134460?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-134460?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-134460 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
web-token jwt-experimentalfrom 3.3.0 before 3.4.10
web-token jwt-experimentalfrom 4.0.0 before 4.0.7
web-token jwt-experimentalfrom 4.1.0 before 4.1.7
web-token jwt-frameworkfrom 1.2.0 before 3.4.10
web-token jwt-frameworkfrom 4.0.0 before 4.0.7
web-token jwt-frameworkfrom 4.1.0 before 4.1.7

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6vvh-pxr4-25r7Packagistweb-token/jwt-experimental<=4.1.6no fix published
GHSA-6vvh-pxr4-25r7Packagistweb-token/jwt-library<3.4.103.4.10
GHSA-6vvh-pxr4-25r7Packagistweb-token/jwt-library>=4.0.0 <4.0.74.0.7
GHSA-6vvh-pxr4-25r7Packagistweb-token/jwt-library>=4.1.0 <4.1.74.1.7

Attack patterns (CAPEC)

  • CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
  • CAPEC-14 Client-side Injection-induced Buffer Overflow Likelihood: Medium · Severity: High
  • CAPEC-39 Manipulating Opaque Client-based Data Tokens Likelihood: High · Severity: Medium
  • CAPEC-74 Manipulating State Likelihood: Medium · Severity: High
  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-389 Content Spoofing Via Application API Manipulation Severity: Low
  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON