CVE-2026-71195: Critical severity Openstack Manila vulnerability
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: allowaccess: grant data-plane read/write access to another tenant's share; denyaccess: revoke the owner's existing access rules; updateaccess: escalate access level (e.g., ro to rw); createsharebackup: exfiltrate share data via a backup created under the attacker's project; softdelete: 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
OpenStack Manilato a version that resolves this vulnerability.Fixed in 23.0.1
Event History
Frequently Asked Questions
Who can exploit this issue?
Any authenticated member of an OpenStack project can exploit the affected API operations against any public Manila share. The attacker does not need to belong to the share owner's project because the UUID is visible for public shares.
Which shares are exposed?
The issue affects public shares. The affected operations load a foreign public share after authorizing against the caller's own project context, without re-authorizing against the share owner's project.
What could an attacker do?
An attacker can add, revoke, or escalate share access rules; create a backup under their own project to exfiltrate share data; soft-delete or restore a foreign share; alter export-location metadata; and list access rules containing IP addresses, usernames, and CephFS keys.
What version addresses the issue?
OpenStack Manila versions before 23.0.1 are affected. Upgrading to 23.0.1 or later addresses the stated affected-version range.