OpenStack Manila
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1.0.0, < 20.0.3
- >= 21.0.0, < 21.0.3
- >= 22.0.0, < 22.0.2
- >= 23.0.0, < 23.0.1
Fixed in 20.0.3, 21.0.3, 22.0.2, 23.0.1
Mitigation
Upgrade Manila to 20.0.3 or 21.0.3 or 22.0.2 or 23.0.1 or later.
References
- Vendor advisory openwall.com/lists/oss-security/2026/10/20/18
- Vendor advisory security.openstack.org/ossa/OSSA-2026-046.html
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| CVE record (tagged exploit) | https://bugs.launchpad.net/ossa/+bug/2161412 | unknown | 14 Nov 2026 |