CVE-2026-92091

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-80228 (ENISA EUVD)Source: ENISA EUVD

5.9EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 5.9Exploit: No code on recordExposed services: Not assessed

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

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.9MEDIUMmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 16, 2026

Last Modified

September 16, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
No fix on record yet. Sources: redhat, github.
GitHub advisoryMentions a patch (unverified)

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
Red Hat

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
Red HatMentions a patch (unverified)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-jwcrypto1.1.0-1 ... 1.5.6-1.2 (7 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-jwcrypto1.5.6-1, 1.5.6-1.1, 1.5.6-1.1~deb13u1, 1.5.6-1.2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-jwcrypto1.5.6-1, 1.5.6-1.1, 1.5.6-1.1~deb13u1, 1.5.6-1.2
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 76 is merged into the row it repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  6. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  7. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  8. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-10-25 13:50 UTCEG score recompute
  10. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  11. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-10-22 12:30 UTCEG score recompute
  14. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  15. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  16. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  17. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-10-18 03:00 UTCEG score recompute
  19. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  20. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  24. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-10-12 14:45 UTCEG score recompute
Show 50 more
  1. 2026-10-11 19:13 UTCEG score recompute
  2. 2026-10-11 16:29 UTCEG score recompute
  3. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-10-11 13:44 UTCEG score recompute
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  6. 2026-10-10 18:37 UTCEG score recompute
  7. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  8. 2026-10-08 20:48 UTCEG score recompute
  9. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-06 20:41 UTCEG score recompute
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  13. 2026-10-05 21:49 UTCEG score recompute
  14. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  16. 2026-10-03 23:50 UTCEG score recompute
  17. 2026-10-03 00:54 UTCEG score recompute
  18. 2026-10-02 02:00 UTCEG score recompute
  19. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  20. 2026-10-01 03:07 UTCEG score recompute
  21. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  22. 2026-09-30 04:14 UTCEG score recompute
  23. 2026-09-29 05:21 UTCEG score recompute
  24. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  25. 2026-09-28 06:28 UTCEG score recompute
  26. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  27. 2026-09-27 07:35 UTCEG score recompute
  28. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  29. 2026-09-26 08:41 UTCEG score recompute
  30. 2026-09-25 09:48 UTCEG score recompute
  31. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  32. 2026-09-24 10:55 UTCEG score recompute
  33. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  34. 2026-09-23 12:02 UTCEG score recompute
  35. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  36. 2026-09-22 13:08 UTCEG score recompute
  37. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  38. 2026-09-21 14:15 UTCEG score recompute
  39. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  40. 2026-09-19 16:28 UTCEG score recompute
  41. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  42. 2026-09-18 17:35 UTCEG score recompute
  43. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  44. 2026-09-16 19:45 UTCEG score recompute
  45. 2026-09-16 15:26 UTCEG score recompute
  46. 2026-09-16 15:01 UTCEG score recompute
  47. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  48. 2026-09-16 08:26 UTCEG score recompute
  49. 2026-09-16 07:45 UTCEG score recomputeFirst assessed: 5.9 MEDIUM
  50. 2026-09-16 07:41 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-92091?
CVE-2026-92091 is a medium-severity vulnerability; its CVE record was published on September 16, 2026. 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…
When was CVE-2026-92091 made public?
CVE-2026-92091 was made public on September 16, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on September 16, 2026. EchelonGraph's copy of the record carries a last-modified date of September 16, 2026; the record at its source may have been updated since.
Is CVE-2026-92091 actively exploited?
CVE-2026-92091 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92091?
CVE-2026-92091 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92091?
No fix for CVE-2026-92091 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs