Skip to main content
Vulnerability Database/CVE-2026-71195

CVE-2026-71195: OpenStack Manila Auth Bypass Vulnerability

CVE-2026-71195 is an authentication bypass flaw in OpenStack Manila that allows unauthorized access to public shares. Attackers can grant access, revoke permissions, and exfiltrate data from shares they do not own. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-71195 Overview

CVE-2026-71195 is a broken authorization flaw [CWE-863] in OpenStack Manila before version 23.0.1. Multiple Manila API operations on public shares fail to verify that the caller owns the share. 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. Any authenticated project member can abuse these operations against any public share, because the share UUID is visible by design.

Critical Impact

Authenticated tenants can read, modify, and exfiltrate data from foreign public shares, revoke owner access, disclose CephFS keys, and disrupt deletion workflows across the shared file service.

Affected Products

  • OpenStack Manila versions prior to 23.0.1
  • Deployments exposing public shares through the Manila API
  • Shared File Systems service in multi-tenant OpenStack clouds

Discovery Timeline

  • 2026-10-21 - CVE-2026-71195 published to the National Vulnerability Database
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-71195

Vulnerability Analysis

OpenStack Manila provides shared file systems to tenants. Shares marked as public are visible to all projects for discovery and mounting under the owner's access policy. The vulnerability stems from controllers that enforce policy against the caller's project but operate on the share object belonging to a different project. The authorization decision never re-evaluates ownership of the target resource.

The following API operations are affected: allow_access grants data-plane read or write access to another tenant's share. deny_access revokes the owner's existing access rules. update_access escalates an access level from read-only to read-write. create_share_backup exfiltrates share data via a backup created under the attacker's project. soft_delete moves a foreign share to the recycle bin, and restore interferes with the owner's deletion workflow. Export location metadata operations create, update, and delete metadata on foreign export locations. Access rule listing discloses IP addresses, usernames, and CephFS keys.

Root Cause

The root cause is incorrect authorization scoping in the API controllers. Policy checks confirm that the caller holds the required role within their own project, then the controller loads a foreign share by UUID without a second ownership check against the share's project_id. This matches the classic [CWE-863] pattern of incorrect authorization.

Attack Vector

An authenticated project member obtains the UUID of any public share through standard share listing. The attacker then calls the vulnerable endpoints with that UUID. Because the controller only validates the caller's project context, Manila executes the operation against the foreign share. Exfiltration via create_share_backup is particularly dangerous because the backup lands in the attacker's project namespace.

See the OpenStack Security Advisory OSSA-2026-046 and the Launchpad Bug Report #2161412 for technical details.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-71195

Indicators of Compromise

  • Manila API calls from project A targeting share UUIDs owned by project B, visible in manila-api logs with mismatched project_id fields.
  • Unexpected create_share_backup jobs referencing shares that do not belong to the requesting project.
  • New or modified access rules on public shares that do not correlate with the share owner's activity.
  • Unexplained appearance of foreign shares in a tenant's recycle bin following soft_delete calls.

Detection Strategies

  • Parse Manila API audit logs and alert when the request project_id differs from the target share's project_id for the affected operations.
  • Correlate access rule changes against share ownership metadata to flag cross-tenant mutations.
  • Monitor backup creation events and compare the backup owner project with the source share owner project.

Monitoring Recommendations

  • Forward manila-api and manila-share logs to a centralized analytics pipeline for cross-tenant correlation.
  • Track CephFS key disclosures and rotate any keys returned to unauthorized projects.
  • Baseline normal public share access patterns per tenant and alert on deviations such as sudden access rule enumeration.

How to Mitigate CVE-2026-71195

Immediate Actions Required

  • Upgrade OpenStack Manila to version 23.0.1 or later, which enforces ownership re-authorization on affected endpoints.
  • Audit all existing public shares for unauthorized access rules, backups, or metadata changes and revert unexpected modifications.
  • Rotate CephFS keys and any credentials that may have been exposed through access rule listing.
  • Review backup storage for artifacts created by non-owner projects and remove unauthorized copies.

Patch Information

The fix is included in OpenStack Manila 23.0.1 and later. Operators running earlier branches should apply the backports referenced in OSSA-2026-046. Additional distribution patches are tracked through the Openwall OSS Security notice.

Workarounds

  • Disable public shares by setting shares to private until the patch is applied, removing the attack surface for UUID-based abuse.
  • Restrict Manila API access through network policy so only trusted tenants can reach affected endpoints during the remediation window.
  • Apply stricter oslo.policy rules that require matching project_id for allow_access, deny_access, update_access, create_share_backup, soft_delete, and restore where feasible.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.