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.3% (25th 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
Trending — 4 sources updated this weekElevated
7.1EG
EchelonGraph verdictPlan mitigationRemediate 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.3%CVSS: 7.1Exploit: 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.

The CVE record's CNA (MITRE Corporation) lists OpenStack Mistral versions before 20.1.1, 21.0.0 up to but not including 21.0.1 and 22.0.0 up to but not including 22.0.1 as affected. No release containing a fix is confirmed on record.

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 v3
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 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 (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
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. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
25th
KEV
Not listed

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. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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.

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
No fix on record yet.
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 (17 versions)
  • 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 27× in last 7d / 27× 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.

  1. 2026-10-13 04:22 UTCEG score recompute
  2. 2026-10-13 04:22 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  3. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-10-12 14:42 UTCEG score recompute
  5. 2026-10-11 19:53 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  6. 2026-10-11 19:12 UTCEG score recompute
  7. 2026-10-11 16:28 UTCEG score recompute
  8. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  9. 2026-10-11 13:41 UTCEG score recompute
  10. 2026-10-11 08:50 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  11. 2026-10-10 21:45 UTCEG score recompute
  12. 2026-10-10 21:45 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-10-10 10:41 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  15. 2026-10-09 23:37 UTCEG score recompute
  16. 2026-10-09 23:37 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  17. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-09 12:34 UTCEG score recompute
  19. 2026-10-09 12:34 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  20. 2026-10-09 11:54 UTCEG score recompute
  21. 2026-10-09 11:54 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  22. 2026-10-09 08:19 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  23. 2026-10-08 21:16 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
  24. 2026-10-08 18:36 UTCEG score recompute
  25. 2026-10-08 18:36 UTCGHSA enrichmentGHSA-858j-2m97-g3qm · GitHub severity HIGH
Show 2 more
  1. 2026-10-08 17:46 UTCEG score recomputeFirst assessed: 7.1 HIGH
  2. 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.3% probability of exploitation in the next 30 days (25th 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?
No fix for CVE-2026-93860 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (MITRE Corporation) lists OpenStack Mistral versions before 20.1.1, 21.0.0 up to but not including 21.0.1 and 22.0.0 up to but not including 22.0.1 as affected. No release containing a fix is confirmed on record. 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