CVE-2026-92091

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw was found in jwcrypto. The JWK.import_key() function validates the key_ops JWK member for duplicate values using an algorithm with O(n^2) time complexity, and the length of key_ops is not bounded. A remote, unauthenticated attacker can supply a JWK with a large key_ops array to an application that passes attacker-controlled key material to a public key-import API (reachable via ECDH-ES key agreement, OIDC dynamic client registration, DPoP, or ACME account key registration, among others) to consume excessive CPU time, resulting in a denial of service.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
42%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 16, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
🔬 Proof of concept available. Patch available. Sources: redhat, github.
github Patch Available🟡 PoC Available

Quadratic key_ops duplicate check in JWK.import_key allows CPU-exhaustion DoS · Advisory · latchset/jwcrypto · GitHub

https://github.com/latchset/jwcrypto/security/advisories/GHSA-pwgw-f7xr-863h
redhat

2533849 – (CVE-2026-92091) CVE-2026-92091 jwcrypto: jwcrypto: denial of service via O(n^2) duplicate check on unbounded JWK key_ops array

https://bugzilla.redhat.com/show_bug.cgi?id=2533849
redhat Patch Available

CVE-2026-92091 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-92091

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 17:35 UTCEG score recompute
  3. 2026-09-17 19:32 UTCEPSS rescore
  4. 2026-09-16 19:45 UTCEG score recompute
  5. 2026-09-16 15:26 UTCEG score recompute
  6. 2026-09-16 15:01 UTCEG score recompute
  7. 2026-09-16 14:09 UTCEPSS rescore
  8. 2026-09-16 08:26 UTCEG score recompute
  9. 2026-09-16 07:45 UTCEG score recompute
  10. 2026-09-16 07:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92091?
CVE-2026-92091 is a medium vulnerability published on September 16, 2026. A flaw was found in jwcrypto. The JWK.importkey() function validates the keyops JWK member for duplicate values using an algorithm with O(n^2) time complexity, and the length of keyops is not bounded. A remote, unauthenticated attacker can supply a JWK with a large keyops array to an application…
When was CVE-2026-92091 disclosed?
CVE-2026-92091 was first published in the National Vulnerability Database on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92091 actively exploited?
CVE-2026-92091 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 58.4% of all scored CVEs.
What is the CVSS score of CVE-2026-92091?
CVE-2026-92091 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-92091?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92091, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92091

Explore →

Is Your Infrastructure Affected by CVE-2026-92091?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs