CVE-2026-71195: critical vulnerability in OpenStack Manila
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
48Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 9.9epss 0.5%
from disclosure to weapon6 days
Published on NVDOct 21
1st PoC+6d
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Affected products
OpenStack · Manilapublic PoCs found — 3
githubgithub.com/emirwtz/CVE-2026-71195★ 0githubgithub.com/mehmet-emir-eroglu/CVE-2026-71195★ 0cve_referencebugs.launchpad.net/ossa/+bug/2161412unverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.