CVE-2026-115376 in Incus
Summary
by MITRE • 10/22/2026
Incus 7.0.1 before 7.0.2 and 7.2.0 before 7.5.0 contains an authorization bypass vulnerability that allows project-restricted clients to copy volumes by omitting source.type. Attackers can send crafted POST requests to the custom volumes endpoint with a chosen source.project to copy and read other projects' volumes, snapshots, and configuration.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 10/23/2026
The Incus container management platform contains an authorization bypass vulnerability affecting versions prior to 7.0.2 in the 7.0 series and prior to 7.5.0 in the 7.2 series. This flaw resides within the custom volumes endpoint, specifically during the volume copy operation initiated via POST requests. The core technical deficiency is a failure to enforce source type validation when processing incoming API calls. Specifically, if an attacker omits the source.type field from the request payload, the server fails to properly validate whether the client has permission to access the target project's resources. This logic error allows users who are restricted to specific projects within Incus to bypass those restrictions and interact with volumes belonging to other projects.
From a technical perspective, this vulnerability is classified under CWE-285, which describes Improper Authorization, as well as CWE-798, concerning the use of default credentials or overly permissive configurations that can be exploited when specific constraints are not enforced. The absence of explicit source type validation creates an ambiguity in how the backend interprets the request parameters. When the source.type is missing, the system defaults to a behavior that does not strictly isolate project boundaries for read operations involving volume data. This allows authenticated but restricted clients to specify arbitrary target projects and initiate copy operations against volumes they should not have access to according to their assigned role-based permissions.
The operational impact of this vulnerability is significant in multi-tenant environments where Incus is used to manage isolated containers or virtual machines across different organizational units or customers. An attacker with limited project-level privileges can exploit this flaw to read sensitive data stored within other projects' volumes, including snapshots and configuration files. This constitutes a severe breach of confidentiality and isolation guarantees that are fundamental to container orchestration platforms. The ability to copy these resources effectively grants the attacker unauthorized access to potentially critical application data, database contents, or system configurations belonging to other tenants or internal teams.
This attack vector aligns with MITRE ATT&CK technique T1083, which covers File and Directory Discovery, as well as T1567, Exfiltration Over Web Services, since the attacker can extract data from isolated environments using standard HTTP methods. The vulnerability highlights a critical gap in input validation logic where optional fields are not handled with sufficient security checks to prevent privilege escalation or lateral movement within the platform's project structure.
To mitigate this risk, organizations running Incus must immediately upgrade their infrastructure to version 7.0.2 or later if they are on the 7.0 branch, or to version 7.5.0 or later if they are on the 7.2 branch. These releases include patches that enforce strict validation of source parameters and ensure that project isolation is maintained even when optional fields like source.type are omitted from API requests. Until an upgrade can be performed, administrators should monitor logs for unusual POST requests to custom volume endpoints with missing type indicators and restrict network access to the Incus API if possible. Regular auditing of user permissions and enforcing least-privilege principles across all projects will also help minimize the potential blast radius of such authorization bypasses in future iterations or similar platforms.