# CVE-2026-93861: Missing authorization in Mistral

> Attackers can bypass workflow sharing restrictions to read and execute private workflows from other projects without owner consent.

- **Severity:** Medium 6.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-93861, GHSA-p254-mh9p-hpfm, UBUNTU-CVE-2026-93861

## What is CVE-2026-93861?

CVE-2026-93861 is a medium-severity missing authorization vulnerability in OpenStack Mistral, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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 (Incorrect Authorization)

## Which versions are affected by CVE-2026-93861?


## How do I fix CVE-2026-93861?

Apply the vendor's patch.

## Is CVE-2026-93861 being exploited?

There is no known exploitation of CVE-2026-93861 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93861 and fix it if it is affected.

What it is: CVE-2026-93861 is a medium-severity missing authorization vulnerability in OpenStack Mistral, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93861 in the wild and no public exploit code.

Affected product: OpenStack Mistral. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93861/ (Markdown: https://insights.sbomify.com/CVE-2026-93861/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93861
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93861
- OSV: https://osv.dev/vulnerability/CVE-2026-93861

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93861/
Summaries are generated and may contain mistakes; the official description above is the record.