Skip to main content
Menu
CVEs

jwt-library key recovery via padding oracle in RSA1_5 unwrapping

Affects web-token jwt-framework and jwt-library before 3.4.10, 4.0.x before 4.0.7, and 4.1.x before 4.1.7, when RSA1_5 is registered for decryption and an RSA private key is held. Fixed in 3.4.10, 4.0.7, and 4.1.7.

CVE-2026-134459Published November 21, 2026, updated

8.2HighCNA
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 and jwt-library before 3.4.10, 4.0.x before 4.0.7, and 4.1.x before 4.1.7 contain a padding oracle in RSACrypt::decryptWithRSA15() because RSA1_5 decryption lacks implicit rejection, so invalid padding, wrong CEK length, and valid padding take measurably different time. Remote attackers can submit adaptively crafted JWE encrypted_key values and measure these timing differences to recover the wrapped content encryption key.

Who should check

Teams running web-token jwt-framework or jwt-library 3.x or 4.x that register RSA1_5 for JWE decryption with an RSA private key.

“Applications that register RSA1_5 in their decryption AlgorithmManager and hold an RSA private key.”

github.com

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-134459 (web-token jwt-framework before 3.4.10 RSA1_5 Bleichenbacher Padding Oracle), 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-134459 (entry last updated 2026-11-21):
Affected:
- web-token jwt-library: from 3.3.0, fixed in 3.4.10
- web-token jwt-library: from 4.0.0, fixed in 4.0.7
- web-token jwt-library: from 4.1.0, fixed in 4.1.7
- web-token jwt-framework: 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 that register RSA1_5 in their decryption AlgorithmManager and hold an RSA private key. (source: https://github.com/web-token/jwt-framework/security/advisories/GHSA-5739-39v2-5754)
- Affected versions are web-token jwt-framework and jwt-library 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-before-3.4.10-rsa1-5-bleichenbacher-padding-oracle)
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-134459 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134459 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-5739-39v2-5754
- https://www.vulncheck.com/advisories/web-token-jwt-framework-before-3.4.10-rsa1-5-bleichenbacher-padding-oracle
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-134459
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-134459"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • 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

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · web-token/jwt-framework · Advisory GHSA-5739-39v2-5754
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134459
RecordNVD · CVE-2026-134459
Other links 1
Linkvulncheck.com · advisories/web-token-jwt-framework-before-3.4.10-rsa1-5-bleichenbacher-padding-oracle

Questions about CVE-2026-134459

Is CVE-2026-134459 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 RSA1_5 key-unwrapping code lets an attacker tell padding outcomes apart through timing. With enough adaptive queries, the wrapped content encryption key (CEK) can be recovered.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134459?

jwt-library: from 3.3.0 before 3.4.10. jwt-library: from 4.0.0 before 4.0.7. jwt-library: from 4.1.0 before 4.1.7. jwt-framework: 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 and jwt-library before 3.4.10, 4.0.x before 4.0.7, and 4.1.x before 4.1.7, in applications that register RSA1_5 in their decryption AlgorithmManager and hold an RSA private key. To check, compare the installed package version against these ranges and look for RSA1_5 in the decryption AlgorithmManager configuration.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134459?

Upgrade to 3.4.10, 4.0.7, or 4.1.7, whichever matches the release line in use.

Source: github.com, vulncheck.com

No corrections so far. Something wrong on this page? Report an error.