[OSSA-2026-044] OpenStack Mistral: Four authorization and privilege vulnerabilities in Mistral (CVE-2026-93858, CVE-2026-93860, CVE-2026-93861, CVE-2026-97147))
OpenStack Mistral has four authorization and privilege flaws in OSSA-2026-044.
62
Vulnerability1 · 1 read
CVE-2026-93861
Authorization bypass in OpenStack Mistral workflow sharing
- CVSS 4.0
- 6.0 medium
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
OpenStack Mistral through 23.0.0 has an incorrect-authorization flaw (CWE-863) in the workflow membership API. A project that has already accepted a share of another project's private workflow can create a further membership naming a third project; the new row is stored under the accepting project rather than the original owner, so the owner can neither see nor delete it. The third project can accept that membership even though the owner never granted it, then read and execute the owner's private workflow, and only the intermediate accepting project can later revoke that access. Clouds running Mistral through 23.0.0 that share private workflows are affected. No public proof of concept is known, and the issue is not listed in CISA KEV.
What to do: Apply the OpenStack security fix from OSSA-2026-044 and move Mistral beyond 23.0.0 once a patched release is available. Until then, restrict which projects may accept or create workflow shares, and audit membership rows for shares the workflow owner did not grant. Unexpected access can only be revoked by the intermediate accepting project, not by the owner.
| Product | Affected |
|---|---|
| OpenStack Mistral | through 23.0.0 |
Estimated exposure
nicheNo basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
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.
- Weakness
- CWE-863
- Vector
- CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X