CVE-2026-115370 in Incus
Summary
by MITRE • 10/23/2026
Incus 6.0.5 before 6.0.7, 6.12.0 before 7.0.2, and 7.1.0 before 7.5.0 contains a restriction bypass vulnerability that allows restricted project users to use pull mode migration via clustered refresh requests. Attackers with instance creation rights can send a refresh migration request for an existing instance to make the server open outbound TLS websocket connections and probe reachable services.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 10/23/2026
The identified vulnerability in Incus versions prior to 6.0.7, 6.12.2, and 7.5.0 represents a critical restriction bypass within the container orchestration platform's access control mechanisms. This flaw specifically impacts users operating under restricted project configurations who possess instance creation privileges but are otherwise intended to have limited network capabilities. The core technical deficiency lies in how the system handles clustered refresh requests during pull mode migrations. When such a request is initiated, the Incus server opens outbound TLS websocket connections without adequately verifying whether the initiating user has explicit permission for external network access or migration operations beyond their assigned scope. This architectural oversight allows an attacker to leverage the instance creation right as a vector to trigger these privileged network actions, effectively circumventing the intended security boundaries of restricted projects.
From a technical perspective, this vulnerability enables what is known as a server-side request forgery variant through managed infrastructure components. By sending a refresh migration request for an existing instance, the attacker forces the Incus daemon to establish outbound connections to arbitrary destinations defined in the migration target configuration. These connections utilize TLS websocket protocols, which can be used to probe internal network services that are otherwise inaccessible from outside the container environment or restricted project sandbox. The ability to initiate these probes means that attackers can perform reconnaissance against backend databases, internal APIs, management interfaces, and other critical infrastructure components residing on the host network or within adjacent virtualized environments. This transforms a seemingly benign administrative operation into a powerful tool for lateral movement and service discovery.
The operational impact of this vulnerability is severe, particularly in multi-tenant cloud environments where Incus is deployed to isolate workloads across different customers or departments. An attacker with low-level privileges can escalate their reach from an isolated container to the broader network infrastructure controlled by the Incus cluster. This capability facilitates unauthorized access to sensitive data stored on internal services, allows for further exploitation of vulnerabilities in those targeted services, and potentially leads to full compromise of the underlying host system if combined with other exploits. In a clustered environment, this can also disrupt service availability or lead to data exfiltration through covert channels established via these outbound connections. The lack of proper authorization checks on pull mode migration requests undermines the fundamental security model of project-based isolation in Incus.
This vulnerability aligns closely with CWE-284 Improper Access Control and CWE-918 Server-Side Request Forgery, as it involves bypassing intended restrictions to perform unauthorized network interactions initiated by a server component under attacker influence. In terms of the MITRE ATT&CK framework, this behavior corresponds to T1071 Application Layer Protocol for command and control or data exfiltration channels, specifically leveraging TLS websocket connections which can mimic legitimate traffic patterns to evade detection. It also relates to T1598 Phishing for Information within Infrastructure Services if used in conjunction with social engineering, though primarily it serves as a mechanism for internal network discovery via T1046 Network Service Discovery.
To mitigate this risk, organizations running affected versions of Incus must immediately upgrade to version 6.0.7 or later, 6.12.2 or later, or 7.5.0 and beyond where these access control checks have been properly implemented. Until an upgrade is feasible, administrators should restrict instance creation privileges for users in restricted projects who do not require migration capabilities. Additionally, implementing strict network segmentation policies at the host level can limit the impact of outbound connections initiated by compromised containers. Monitoring logs for unusual patterns of pull mode migration requests or unexpected outbound TLS websocket connections from Incus daemons can also aid in early detection and response to potential exploitation attempts.