# CVE-2026-71195: In OpenStack Manila before 23.0.1, multiple Manila API operations on public shares do not verify that the caller owns the share.


- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-71195, GHSA-xm2x-8fhq-8hpv, UBUNTU-CVE-2026-71195

## What is CVE-2026-71195?

CVE-2026-71195 is a critical vulnerability in OpenStack Manila, published on 21 Oct 2026. 

### Official description

In OpenStack Manila before 23.0.1, multiple Manila API operations on public shares do not verify that the caller owns the share. The API controllers authorize operations against the caller's own project context, then load a foreign public share without re-authorizing against the share's actual owner. This affects the following operations: allow_access: grant data-plane read/write access to another tenant's share; deny_access: revoke the owner's existing access rules; update_access: escalate access level (e.g., ro to rw); create_share_backup: exfiltrate share data via a backup created under the attacker's project; soft_delete: move a foreign share to the recycle bin; restore: interfere with the owner's deletion workflow; export location metadata: create, update, and delete metadata on foreign export locations; access rule listing: disclose IPs, usernames, and CephFS keys. Any authenticated project member can exploit these operations on any public share. The share UUID is visible since the share is public.

Weakness: CWE-863 (Incorrect Authorization)

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


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

No fix has been published for CVE-2026-71195 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-71195 being exploited?

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

Public exploit code:

- Offline Python detector for CVE-2026-71195 exposure in OpenStack Manila, with branch-aware rules, CSV/JSON inventories, and auditable reports. (github_poc): https://github.com/mehmet-emir-eroglu/CVE-2026-71195

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71195 is a critical vulnerability in OpenStack Manila, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-71195 exists.

Affected product: OpenStack Manila. 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-71195/ (Markdown: https://insights.sbomify.com/CVE-2026-71195/index.md)
```

## Sources

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

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