Skip to main content
Menu
CVEs

jwt-library denial of service in PBES2 key unwrapping

Only applications that register a PBES2-HS*+A*KW algorithm in their decryption AlgorithmManager are affected. Fixed in jwt-framework 3.4.10, 4.0.7 and 4.1.7.

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

8.7HighCNA
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.0 before 4.0.7, and 4.1.0 before 4.1.7 contain an uncontrolled resource consumption vulnerability in PBES2AESKW::unwrapKey(), which passes the attacker-controlled p2c JWE header value to hash_pbkdf2() without an upper bound. Unauthenticated attackers can send a JWE using a PBES2-HS*+A*KW algorithm with a huge p2c iteration count to force lengthy PBKDF2 computations and exhaust server CPU.

Who should check

Teams running web-token jwt-framework or jwt-library 3.x (before 3.4.10), 4.0.x (before 4.0.7) or 4.1.x (before 4.1.7) that decrypt JWEs with PBES2-HS*+A*KW algorithms

“Applications that register any PBES2-HS*+A*KW algorithm in their decryption AlgorithmManager”

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-134461 (Web-Token jwt-framework before 3.4.10 DoS via Unbounded PBES2 p2c Iteration Count), 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-134461 (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 a PBES2-HS*+A*KW algorithm in their decryption AlgorithmManager (source: https://github.com/web-token/jwt-framework/security/advisories/GHSA-3prj-6hqw-cm82)
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-134461 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134461 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-3prj-6hqw-cm82
- https://www.vulncheck.com/advisories/web-token-jwt-framework-before-3.4.10-dos-via-unbounded-pbes2-p2c-iteration-count
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-134461
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-134461"}.

Affected versions

cve.now Index

26Pof 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.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 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-3prj-6hqw-cm82
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134461
RecordNVD · CVE-2026-134461
Other links 1
Linkvulncheck.com · advisories/web-token-jwt-framework-before-3.4.10-dos-via-unbounded-pbes2-p2c-iteration-count

Questions about CVE-2026-134461

Is CVE-2026-134461 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?

PBES2 decryption uses a PBKDF2 iteration count (p2c) that comes from the token. The library did not limit this count, so a crafted token can force lengthy PBKDF2 computations that use up server CPU.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134461?

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 jwt-framework versions before 3.4.10, from 4.0.0 before 4.0.7, and from 4.1.0 before 4.1.7, but only in applications that register a PBES2-HS*+A*KW algorithm in their decryption AlgorithmManager. To check, look at the installed jwt-framework version and whether the application registers these PBES2 algorithms in that AlgorithmManager.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134461?

Upgrade to 3.4.10 on the 3.x line, 4.0.7 on the 4.0 line, or 4.1.7 on the 4.1 line.

Source: github.com, vulncheck.com

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