CVE-2026-115373 in Incus
Summary
by MITRE • 10/23/2026
Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 contains a missing authorization vulnerability in GET /1.0/operations/{uuid} that lets project-restricted clients read operations in other projects. Attackers holding a restricted certificate and a known operation UUID can retrieve command lines, environment secrets, websocket secrets, and trust enrolment tokens.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 10/23/2026
The identified vulnerability represents a critical authorization failure within the Incus container management platform affecting versions prior to 6.0.7, 6.1.0 through 7.0.2, and 7.1.0 through 7.5.0. This flaw specifically targets the GET /1.0/operations/{uuid} endpoint, which is designed to retrieve status details for background operations such as container creation, snapshots, or migrations. The core technical deficiency lies in the server-side validation logic that fails to enforce project-level isolation when processing requests from clients authenticated with restricted certificates. In a properly secured multi-tenant environment, Incus utilizes projects to isolate resources and permissions among different users or teams. However, this vulnerability allows an attacker who possesses a valid certificate scoped to a specific project to bypass these boundaries if they can guess or obtain the universally unique identifier of an operation running in a different, restricted project.
The operational impact of this flaw is severe due to the sensitive nature of the data exposed through the operations endpoint. When an unauthorized client queries this endpoint using a known UUID from another project, the server returns detailed execution context information rather than denying access or returning generic errors. This includes command lines that may contain hardcoded credentials or secrets, environment variables populated with API keys and authentication tokens, websocket secrets required for establishing persistent connections to container consoles, and trust enrolment tokens used for adding new nodes to a cluster securely. The exposure of these elements effectively grants the attacker significant insight into the internal workings of the Incus infrastructure and potentially provides the cryptographic material necessary to hijack active sessions or compromise other containers within the same host or cluster.
From a classification perspective, this vulnerability aligns with CWE-284 Improper Access Control, specifically illustrating a failure in enforcing object-level access restrictions based on user roles or project scopes. It also maps directly to MITRE ATT&CK technique T1078 Valid Accounts, as the attacker leverages legitimate but restricted credentials to perform unauthorized actions that exceed their intended privileges. The ability to read operations across projects constitutes an escalation of privilege within the application logic, allowing lateral movement and information disclosure that undermines the fundamental security model of multi-tenancy in cloud-native container orchestration systems.
Mitigation for this vulnerability requires immediate upgrading to Incus version 6.0.7 or later, 7.0.2 or later for the 6.1 branch, and 7.5.0 or later for the 7.1 branch. These releases contain patches that enforce strict project-scoped authorization checks on all operation-related API endpoints. In addition to upgrading, administrators should audit their certificate policies to ensure that restricted certificates are granted only the minimum necessary permissions required for specific tasks. Implementing network segmentation and firewall rules to restrict access to the Incus daemon port can also reduce the attack surface by limiting which hosts or users can interact with the management interface directly. Regular monitoring of API logs for unusual patterns, such as repeated requests for operation statuses across different projects, may help detect exploitation attempts in real-time before significant data exfiltration occurs.