---
id: "CVE-2026-71195"
kind: "vulnerability"
aliases: ["CVE-2026-71195"]
title: "OpenStack Manila: any project member can control other tenants' public shares"
severity: "critical"
cvss: 9.9
epss: 0.00484
exploited: false
status: "open"
category: "infrastructure"
products: [{"name": "manila", "fixed": ["20.0.3", "21.0.3", "22.0.2", "23.0.1"], "affected": ">=1.0.0 <20.0.3, >=21.0.0 <21.0.3, >=22.0.0 <22.0.2, ==23.0.0", "ecosystem": "openstack"}]
ecosystems: ["openstack"]
tags: ["cephfs", "infrastructure", "manila", "openstack", "self-hosted", "shared-file-storage"]
not_affected_if: ["managed-hosting", "no-public-shares", "single-tenant"]
published_at: "2026-10-21T06:16:49+00:00"
first_seen_at: "2026-10-23T21:57:28+00:00"
updated_at: "2026-10-24T13:15:54+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-71195", "first_seen_at": "2026-10-23T21:57:28+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-23T22:51:59+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-71195", "first_seen_at": "2026-10-24T13:15:54+00:00"}]
---

# OpenStack Manila: any project member can control other tenants' public shares

OpenStack Manila API calls on public shares authorize against the caller's own project and never re-check the share's owner. Any authenticated project member can grant, deny or escalate access rules, read access rules (IPs, usernames, CephFS keys), back up, soft-delete or restore another tenant's public share. Separately, the export-location metadata API does not scope its lookup to the share in the request, so one project can read, change or delete another's metadata. Two issues share this CVE; the metadata one is easier to exploit with public shares.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- openstack:manila affected >=1.0.0 <20.0.3, >=21.0.0 <21.0.3, >=22.0.0 <22.0.2, ==23.0.0 fixed 20.0.3, 21.0.3, 22.0.2, 23.0.1

## How to check

Run 'pip show manila' or 'manila-manage --version' on API nodes and compare against the fixed versions. You are exposed if you run Manila at any version below 20.0.3, 21.0.3, 22.0.2 or 23.0.1 (the advisory's affects ranges). The public-share issues need shares with is_public=true: run 'openstack share list --all-projects --public'. The metadata issue affects any deployment that uses export-location metadata.

## Fix

Upgrade to Manila 23.0.1, 22.0.2, 21.0.3 or 20.0.3. Backport patches are in Gerrit (review.opendev.org/1011478, 1011479, 1011481, 1011482, 1011483). Until then, set shares to private. If CephFS keys may have been read, rotate them and review the access rules.

## Timeline

- 2026-10-23T21:57:28+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-71195
- 2026-10-23T22:51:59+00:00 analyst — Read OSSA-2026-046 (primary): affects Manila >=1.0.0 <20.0.3, >=21.0.0 <21.0.3, >=22.0.0 <22.0.2, ==23.0.0; fixes backported to 2025.1 through 2026.2 stable branches. No exploitation or PoC found; community discussion not searched. 20.0.3 release not confirmed in the Gerrit release commit (it lists 23.0.1, 22.0.2, 21.0.3).
- 2026-10-24T13:15:54+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-71195

## Documents

- [advisory] OSSA-2026-046: Manila allows cross-project public-share and export-metadata changes https://security.openstack.org/ossa/OSSA-2026-046.html
- [describes] oss-security: OSSA-2026-046 Manila (CVE-2026-71195) https://www.openwall.com/lists/oss-security/2026/10/20/18
- [fix] [security] Release manila 23.0.1, 22.0.2, 21.0.3 https://review.opendev.org/q/31b856b2a4b37b681410f154a52861a5dc1b889e

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_