jwt-library token decryption via weak ConcatKDF in ECDH-ES
Affects jwt-framework before 3.4.12, and 4.0.x before 4.0.8, 4.1.x before 4.1.10, 4.2.x before 4.2.4, for ECDH-ES JWEs with A256CBC-HS512 or A192CBC-HS384. Fixed in 3.4.12, 4.0.8, 4.1.10 and 4.2.4.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.4.12, 4.0.8, 4.1.10, 4.2.4
- Who is exposed
- Not reported
Summary
Written by a model
web-token jwt-framework and jwt-library before 3.4.12, 4.0.x before 4.0.8, 4.1.x before 4.1.10, and 4.2.x before 4.2.4, and jwt-encryption-algorithm-ecdh-es through 3.2.10, have a ConcatKDF::generate() that performs a single SHA-256 round, deriving at most 32 bytes for ECDH-ES and ECDH-SS direct key agreement. Anyone holding a JWE using A256CBC-HS512 can decrypt it under an all-zero AES key, while A192CBC-HS384 content keys have only 64-bit strength.
Who should check
Teams running web-token jwt-library, jwt-framework or jwt-encryption-algorithm-ecdh-es that produce JWEs with ECDH-ES and A256CBC-HS512 or A192CBC-HS384.
Not fixed by: Upgrading does not protect tokens already produced with these algorithms.
“JWE produced with alg set to ECDH-ES and enc set to A256CBC-HS512”
What to do
Upgrade to a fixed version: 3.4.12, 4.0.8, 4.1.10, 4.2.4.
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-134458 (web-token jwt-framework before 3.4.12 ECDH-ES Weak Key Derivation via ConcatKDF), 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-134458 (entry last updated 2026-11-21):
Affected:
- web-token jwt-library: from 3.3.0, fixed in 3.4.12
- web-token jwt-library: from 4.0.0, fixed in 4.0.8
- web-token jwt-library: from 4.1.0, fixed in 4.1.10
- web-token jwt-library: from 4.2.0, fixed in 4.2.4
- web-token jwt-framework: fixed in 3.4.12
- web-token jwt-framework: from 4.0.0, fixed in 4.0.8
- web-token jwt-framework: from 4.1.0, fixed in 4.1.10
- web-token jwt-framework: from 4.2.0, fixed in 4.2.4
- web-token jwt-encryption-algorithm-ecdh-es: from 1.2.0, through 3.2.10
Fixed versions: 3.4.12, 4.0.8, 4.1.10, 4.2.4.
Conditions (all must be true for the bug to be hit):
- JWE produced with alg set to ECDH-ES (direct key agreement) and enc set to A256CBC-HS512 or A192CBC-HS384, whatever the curve. (source: https://github.com/web-token/jwt-framework/security/advisories/GHSA-5pj7-wx9m-cjh6)
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-134458 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134458 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-5pj7-wx9m-cjh6
- https://www.vulncheck.com/advisories/web-token-jwt-framework-before-3.4.12-ecdh-es-weak-key-derivation-via-concatkdf
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-134458
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-134458"}.Affected versions
- web-token jwt-libraryFrom 3.3.0 · fixed in 3.4.12
- web-token jwt-libraryFrom 4.0.0 · fixed in 4.0.8
- web-token jwt-libraryFrom 4.1.0 · fixed in 4.1.10
- web-token jwt-libraryFrom 4.2.0 · fixed in 4.2.4
- web-token jwt-frameworkfixed in 3.4.12
- web-token jwt-frameworkFrom 4.0.0 · fixed in 4.0.8
- web-token jwt-frameworkFrom 4.1.0 · fixed in 4.1.10
- web-token jwt-frameworkFrom 4.2.0 · fixed in 4.2.4
- web-token jwt-encryption-algorithm-ecdh-esFrom 1.2.0 · through 3.2.10
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
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 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-5pj7-wx9m-cjh6 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134458 |
| Record | NVD · CVE-2026-134458 |
| Other links 1 | |
| Link | vulncheck.com · advisories/web-token-jwt-framework-before-3.4.12-ecdh-es-weak-key-derivation-via-concatkdf |
Questions about CVE-2026-134458
Is CVE-2026-134458 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?
When a JWE uses alg ECDH-ES with enc A256CBC-HS512 or A192CBC-HS384, the content is weakly protected, and anyone who obtains the token can decrypt it without the recipient's private key. For A192CBC-HS384 the content key has only 64 bits of strength.
Source: github.com
Which versions are affected by CVE-2026-134458?
jwt-library: from 3.3.0 before 3.4.12. jwt-library: from 4.0.0 before 4.0.8. jwt-library: from 4.1.0 before 4.1.10. jwt-library: from 4.2.0 before 4.2.4. jwt-framework: before 3.4.12. 4 more packages are listed on the page.
Source: cve.now feed data
Am I affected, and how do I check?
Affected are jwt-framework before 3.4.12, and the 4.0.x, 4.1.x and 4.2.x lines before 4.0.8, 4.1.10 and 4.2.4. To check, compare the installed jwt-framework version with these ranges and check whether tokens are produced with alg ECDH-ES and enc A256CBC-HS512 or A192CBC-HS384.
Source: github.com
How do I fix CVE-2026-134458?
Upgrade jwt-framework to 3.4.12, 4.0.8, 4.1.10 or 4.2.4, matching the release line in use.
Source: github.com
Related
No corrections so far. Something wrong on this page? Report an error.