jwt-experimental missing integrity check in ChaCha20-Poly1305 key encryption
Only applications that register the experimental Chacha20Poly1305 key-encryption algorithm as a JWE alg are exposed. Fixed in jwt-framework 3.4.10, 4.0.7 and 4.1.7.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.4.10, 4.0.7, 4.1.7
- Who is exposed
- Not reported
Summary
Written by a model
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.
Who should check
Teams running web-token jwt-experimental or jwt-framework before 3.4.10, 4.0.7 or 4.1.7 that register the experimental Chacha20Poly1305 JWE alg.
“web-token jwt-framework 1.2.0 before 3.4.10”
What to do
Upgrade to a fixed version: 3.4.10, 4.0.7, 4.1.7.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134460 (web-token jwt-framework 1.2.0 before 3.4.10 Missing Authentication in Chacha20Poly1305 Key Encryption), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134460 (entry last updated 2026-11-21):
Affected:
- web-token jwt-experimental: from 3.3.0, fixed in 3.4.10
- web-token jwt-experimental: from 4.0.0, fixed in 4.0.7
- web-token jwt-experimental: from 4.1.0, fixed in 4.1.7
- web-token jwt-framework: from 1.2.0, fixed in 3.4.10
- web-token jwt-framework: from 4.0.0, fixed in 4.0.7
- web-token jwt-framework: from 4.1.0, fixed in 4.1.7
Fixed versions: 3.4.10, 4.0.7, 4.1.7.
Conditions (all must be true for the bug to be hit):
- Applications register the experimental Chacha20Poly1305 key-encryption algorithm as a JWE alg (source: https://github.com/web-token/jwt-framework/security/advisories/GHSA-6vvh-pxr4-25r7)
- Affected versions are web-token jwt-framework 1.2.0 to before 3.4.10, 4.0.x before 4.0.7, and 4.1.x before 4.1.7 (source: https://www.vulncheck.com/advisories/web-token-jwt-framework-1.2.0-before-3.4.10-missing-authentication-in-chacha20poly1305-key-encryption)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134460 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134460 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/web-token/jwt-framework/security/advisories/GHSA-6vvh-pxr4-25r7
- https://www.vulncheck.com/advisories/web-token-jwt-framework-1.2.0-before-3.4.10-missing-authentication-in-chacha20poly1305-key-encryption
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134460
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134460"}.Affected versions
- web-token jwt-experimentalFrom 3.3.0 · fixed in 3.4.10
- web-token jwt-experimentalFrom 4.0.0 · fixed in 4.0.7
- web-token jwt-experimentalFrom 4.1.0 · fixed in 4.1.7
- web-token jwt-frameworkFrom 1.2.0 · fixed in 3.4.10
- web-token jwt-frameworkFrom 4.0.0 · fixed in 4.0.7
- web-token jwt-frameworkFrom 4.1.0 · fixed in 4.1.7
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · web-token/jwt-framework · Advisory GHSA-6vvh-pxr4-25r7 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134460 |
| Record | NVD · CVE-2026-134460 |
| Other links 1 | |
| Link | vulncheck.com · advisories/web-token-jwt-framework-1.2.0-before-3.4.10-missing-authentication-in-chacha20poly1305-key-encryption |
Questions about CVE-2026-134460
Is CVE-2026-134460 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The Chacha20Poly1305 key-encryption algorithm accepts a tampered encrypted content encryption key with no integrity check, so a modified key is not detected.
Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-134460?
jwt-experimental: from 3.3.0 before 3.4.10. jwt-experimental: from 4.0.0 before 4.0.7. jwt-experimental: from 4.1.0 before 4.1.7. jwt-framework: from 1.2.0 before 3.4.10. jwt-framework: from 4.0.0 before 4.0.7. 1 more package is listed on the page.
Source: cve.now feed data
Am I affected, and how do I check?
Affected are web-token jwt-framework 1.2.0 before 3.4.10, 4.0.x before 4.0.7, and 4.1.x before 4.1.7, and jwt-experimental before 3.4.10, 4.0.x before 4.0.7, and 4.1.x before 4.1.7. Check whether an application registers Jose\Experimental\KeyEncryption\Chacha20Poly1305 from web-token/jwt-experimental as a JWE alg.
Source: github.com, vulncheck.com
How do I fix CVE-2026-134460?
Upgrade to jwt-framework or jwt-experimental 3.4.10, 4.0.7, or 4.1.7, matching the release line in use.
Source: github.com, vulncheck.com
Related
- CVE-2026-134461Web-Token jwt-framework before 3.4.10 DoS via Unbounded PBES2 p2c Iteration Count
- CVE-2026-134458web-token jwt-framework before 3.4.12 ECDH-ES Weak Key Derivation via ConcatKDF
- CVE-2026-134459web-token jwt-framework before 3.4.10 RSA1_5 Bleichenbacher Padding Oracle
- CVE-2026-95723Authenticated Local Missing Integrity Verification Vulnerability leads to Local Privilege Escalation in Virtual Intranet Access (VIA) Client
- CVE-2026-49450Joplin desktop Windows auto-updater accepts signed installer from any publisher because app-update.yml has no publisherName
- CVE-2026-130638Path traversal in the object detection dataset preparation tool in AutoGluon Multimodal
No corrections so far. Something wrong on this page? Report an error.