CVE-2026-134460
Received Received - Intake

Missing Integrity Check in JWT Framework

Vulnerability report for CVE-2026-134460, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-21

Last updated on: 2026-11-21

Assigner: VulnCheck

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-21
Last Modified
2026-11-21
Generated
2026-11-21
AI Q&A
2026-11-21
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 9 associated CPEs
Vendor Product Version / Range
web-token jwt-experimental From 3.3.0 (inc) to 3.4.10 (exc)
web-token jwt-experimental From 4.0.0 (inc) to 4.0.7 (exc)
web-token jwt-experimental From 4.1.0 (inc) to 4.1.7 (exc)
web-token jwt-framework From 4.0.0 (inc) to 4.0.7 (exc)
web-token jwt-framework From 4.1.0 (inc) to 4.1.7 (exc)
web-token jwt-framework to 3.4.10 (exc)
web-token jwt-experimental to 3.4.10 (exc)
web-token jwt-experimental to 4.0.7 (exc)
web-token jwt-experimental to 4.1.7 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-353 The product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The vulnerability is in the web-token jwt-framework and jwt-experimental libraries. It involves a missing integrity check in the experimental Chacha20Poly1305 key-encryption algorithm. The algorithm discards the Poly1305 tag during encryption and does not require it during decryption, allowing attackers to modify the encrypted content encryption key without detection.

Detection Guidance

To detect this vulnerability, check if your system uses vulnerable versions of web-token/jwt-framework or jwt-experimental (below 3.4.10, 4.0.7, or 4.1.7). Inspect JWT tokens for missing Poly1305 tags in the header. Use commands like 'composer show web-token/jwt-framework' or 'composer show web-token/jwt-experimental' to check versions.

Impact Analysis

Attackers could intercept and alter tokens in transit, leading to unauthorized access or data tampering. This could compromise the integrity of encrypted data, allowing attackers to manipulate sensitive information without being detected.

Compliance Impact

This vulnerability could violate compliance requirements that mandate data integrity and protection, such as GDPR's integrity principle or HIPAA's security rule. Unauthorized data tampering risks non-compliance and potential legal consequences.

Mitigation Strategies

Update the affected JWT libraries to the latest patched versions: jwt-framework to 3.4.10 or higher, jwt-experimental to 3.4.10 or higher, and versions 4.0.7 or 4.1.7 for 4.x branches. Remove or disable the experimental Chacha20Poly1305 key-encryption algorithm if not required.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-134460. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...