# CVE-2026-93860: Missing authorization in Mistral

> Attackers with valid tokens can bypass policy checks to modify cluster-wide maintenance state, potentially halting workflow processing across all tenants.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/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:** 9 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-93860, GHSA-858j-2m97-g3qm, UBUNTU-CVE-2026-93860

## What is CVE-2026-93860?

CVE-2026-93860 is a high-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 /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.

Weakness: CWE-862 (Missing Authorization)

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


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

Apply the vendor's patch.

## Is CVE-2026-93860 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93860 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93860 is a high-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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93860 exists.

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-93860/ (Markdown: https://insights.sbomify.com/CVE-2026-93860/index.md)
```

## Sources

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

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