In OpenStack Mistral through 23.0.0, the workflow membership API lets a project that has accepted a share of another project's private workflow create a further membership naming a third project. The new membership row is created with its project_id defaulted to the accepting project rather than the original workflow owner, and thus the owner can neither see nor delete it. The third project can accept this membership (that it had not actually been granted by the owner), and then read and execute the owner's private workflow; only the accepting (not the owning) project can later revoke that access.
CVE-2026-93861
MEDIUMPre-NVD 6.06.0Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (16th 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
6.0EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.0Exploit: None knownExposed 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.
- CVSS v3
- 6.0
- EG Score
- 6.0MEDIUMmedium confidence
- EG Risk
- 27EG Risk 27/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)Severity60% × 45%The EG Score, 6.0 of 10.Exploitation0.3% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
- 16th
- 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 none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 8, 2026
Advisory Details (2)
Auto-updated Oct 8, 2026No 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.htmlWeb page
Bug #2161277 “[OSSA-2026-044] Accepted Mistral Workflow Member C...” : Bugs : OpenStack Security Advisory
https://launchpad.net/bugs/2161277Vendor Advisories for CVE-2026-93861(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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| mistral | 15.0.0-1 ... 23.0.0~rc1-2 (36 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| mistral | 20.0.0-2 ... 23.0.0~rc1-2 (17 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| mistral | 20.0.0-2 ... 23.0.0~rc1-2 (16 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× 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.
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-10-12 14:42 UTCEG score recompute
- 2026-10-11 20:35 UTCGHSA enrichmentGHSA-p254-mh9p-hpfm
- 2026-10-11 19:12 UTCEG score recompute
- 2026-10-11 16:28 UTCEG score recompute
- 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-10-11 13:41 UTCEG score recompute
- 2026-10-10 20:49 UTCEG score recompute
- 2026-10-10 20:49 UTCGHSA enrichmentGHSA-p254-mh9p-hpfm
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-10-09 21:03 UTCEG score recompute
- 2026-10-09 21:03 UTCGHSA enrichmentGHSA-p254-mh9p-hpfm
- 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-10-08 21:16 UTCGHSA enrichmentGHSA-p254-mh9p-hpfm
- 2026-10-08 18:36 UTCEG score recompute
- 2026-10-08 18:35 UTCGHSA enrichmentGHSA-p254-mh9p-hpfm
- 2026-10-08 17:46 UTCEG score recomputeFirst assessed: 6.0 MEDIUM
- 2026-10-08 17:44 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
7 shownDebian:12:mistral
Frequently asked(5)
What is CVE-2026-93861?
CVE-2026-93861 is a medium-severity vulnerability; its CVE record was published on October 8, 2026. In OpenStack Mistral through 23.0.0, the workflow membership API lets a project that has accepted a share of another project's private workflow create a further membership naming a third project. The new membership row is created with its project_id defaulted to the accepting project rather than…
When was the CVE record for CVE-2026-93861 published?
The CVE record for CVE-2026-93861 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 8, 2026; the record at its source may have been updated since.
Is CVE-2026-93861 actively exploited?
CVE-2026-93861 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93861?
CVE-2026-93861 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93861?
No fix for CVE-2026-93861 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-93861 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-93861
Is Your Infrastructure Affected by CVE-2026-93861?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.