CVE-2026-93860

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th 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-95129 (ENISA EUVD) · GHSA-858j-2m97-g3qm (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.4%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

In OpenStack Mistral through 23.0.0, the /v2/maintenance API controller clears the request context and calls the maintenance service directly without any policy enforcement. Any holder of a valid Mistral token, regardless of assigned role, can read and change the service's cluster-wide maintenance state. Setting the state to PAUSED stops processing of new workflow and execution objects across all tenant projects until an operator restores it.

CVSS
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
36th
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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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.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).

A fix is available. Apply it within your standard update timelines.

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.

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

October 8, 2026

Last Modified

October 9, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
Patch available.
Web page

OSSA-2026-044: Four authorization and privilege vulnerabilities in Mistral — OpenStack Security Advisories 0.0.1.dev402 documentation

https://security.openstack.org/ossa/OSSA-2026-044.html
Web page

Bug #2162789 “[OSSA-2026-044] Mistral Maintenance Mode Has No Au...” : Bugs : OpenStack Security Advisory

https://launchpad.net/bugs/2162789

Vendor Advisories for CVE-2026-93860(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
mistral15.0.0-1 ... 23.0.0~rc1-2 (37 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
mistral20.0.0-2 ... 23.0.0~rc1-2 (18 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
mistral20.0.0-2 ... 23.0.0~rc1-2 (16 versions)
  • every version up to 23.0.0-2: fixed in 23.0.0-2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 37× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-11-11 04:01 UTCEchelonGraph re-scored
  4. 2026-11-11 04:01 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  5. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-11-10 06:00 UTCEchelonGraph re-scored
  7. 2026-11-10 06:00 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  8. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  13. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-11-03 20:23 UTCEchelonGraph re-scored
  15. 2026-11-03 20:23 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  16. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-11-03 06:48 UTCEchelonGraph re-scored
  18. 2026-11-03 06:48 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  19. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  25. 2026-10-27 21:12 UTCEchelonGraph re-scored
Show 49 more
  1. 2026-10-27 21:12 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  2. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  4. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-10-25 13:49 UTCEchelonGraph re-scored
  6. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  7. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  9. 2026-10-22 11:28 UTCEchelonGraph re-scored
  10. 2026-10-22 11:28 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  11. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  12. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  13. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  14. 2026-10-19 14:02 UTCEchelonGraph re-scored
  15. 2026-10-19 14:01 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  16. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  17. 2026-10-18 02:58 UTCEchelonGraph re-scored
  18. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  19. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  20. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  21. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  22. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-10-13 04:22 UTCEchelonGraph re-scored
  24. 2026-10-13 04:22 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  25. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  26. 2026-10-12 14:42 UTCEchelonGraph re-scored
  27. 2026-10-11 19:53 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  28. 2026-10-11 19:12 UTCEchelonGraph re-scored
  29. 2026-10-11 16:28 UTCEchelonGraph re-scored
  30. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  31. 2026-10-11 13:41 UTCEchelonGraph re-scored
  32. 2026-10-11 08:50 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  33. 2026-10-10 21:45 UTCEchelonGraph re-scored
  34. 2026-10-10 21:45 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  35. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  36. 2026-10-10 10:41 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  37. 2026-10-09 23:37 UTCEchelonGraph re-scored
  38. 2026-10-09 23:37 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  39. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  40. 2026-10-09 12:34 UTCEchelonGraph re-scored
  41. 2026-10-09 12:34 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  42. 2026-10-09 11:54 UTCEchelonGraph re-scored
  43. 2026-10-09 11:54 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  44. 2026-10-09 08:19 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  45. 2026-10-08 21:16 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  46. 2026-10-08 18:36 UTCEchelonGraph re-scored
  47. 2026-10-08 18:36 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  48. 2026-10-08 17:46 UTCEchelonGraph re-scoredFirst assessed: 7.1 HIGH
  49. 2026-10-08 17:44 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-93860?
CVE-2026-93860 is a high-severity vulnerability; its CVE record was published on October 8, 2026. In OpenStack Mistral through 23.0.0, the /v2/maintenance API controller clears the request context and calls the maintenance service directly without any policy enforcement. Any holder of a valid Mistral token, regardless of assigned role, can read and change the service's cluster-wide maintenance…
When was the CVE record for CVE-2026-93860 published?
The CVE record for CVE-2026-93860 was published on October 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-93860 actively exploited?
CVE-2026-93860 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93860?
CVE-2026-93860 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93860?
A fix for CVE-2026-93860 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-93860 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-93860

Explore →

Is Your Infrastructure Affected by CVE-2026-93860?

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

Book a Demo →Browse All CVEs