External risk intelligence

Incus Authorization Bypass Allows Resource Creation and Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-130773

Incus is a container and virtual machine manager typically deployed within internal data centers or private infrastructure. While the management API may be reachable over a network, it is generally restricted to internal administrative access rather than being directly exposed to the public internet. Access requires authentication, limiting the likelihood of arbitrary public exposure.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a critical vulnerability in Incus, a technology used for managing containers and virtual machines. An authorization bypass allows unauthorized users to create resources and potentially execute commands with root privileges on the host system by exploiting specific configurations. This could allow an attacker to gain significant control over affected systems.

  • Bypassed access controls for resource creation.
  • Attackers could gain root access to host systems.
  • Confirm relevance and exposure within your environment.

Attack Path

How an attacker could exploit the issue

An attacker with restricted project user access can initiate an attack by targeting projects that lack specific feature flags. This allows them to create resources in the default, unrestricted project, potentially leading to the execution of arbitrary code or unauthorized access to host files.

  • Requires authenticated, restricted user access.
  • Triggers vulnerability when creating specific project resources.
  • Risk of code execution or host file access.

Live Threat

Current exploitation, exposure, and threat context

Incus versions prior to 7.6.0 contain an authorization bypass flaw that could allow restricted project users to create resources in the unrestricted default project. When supported by the advisory, this could enable attackers to inject scripts that run as root on the host system or read host files through specially crafted volume configurations.

  • Host system access and sensitive files.
  • Restricted user creating unauthorized resources.
  • Root-level script execution or file reading.

Operational Fix

Recommended remediation, mitigation, and detection steps

The authorization bypass in Incus affects project and infrastructure teams responsible for container and virtual machine management. The first practical step is to identify Incus deployments, assess their reachability and criticality, and pinpoint the accountable system owner to plan remediation based on risk.

  • Identify Incus deployments and owners.
  • Verify external network reachability and impact.
  • Plan and coordinate risk-based remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Incus and what does it do?

Incus is an open-source tool used for managing system containers and virtual machines. It allows users to run multiple isolated Linux environments on a single host. Infrastructure and DevOps teams rely on it to simplify the deployment, orchestration, and lifecycle management of these virtualized resources across their server environments.

How does this authorization bypass work in CVE-2026-130773?

This vulnerability, classified as CWE-863 for Incorrect Authorization, allows a restricted user to act outside their intended permissions. By targeting projects that lack certain security feature flags, a user can incorrectly create resources within the unrestricted default project. This escalation allows them to manipulate system configurations that should be beyond their access level.

What actions trigger this vulnerability?

The flaw is triggered when an authenticated user with restricted permissions performs specific resource creation tasks, such as setting up bridge networks or custom volumes with particular arguments. Notably, the vulnerability does not occur in projects that have the appropriate security feature flags enabled, as those flags properly enforce the intended authorization boundaries.

Do I need to worry about this if my Incus setup is internal?

While Halo Surface Signal indicates that Incus is typically deployed in internal, private infrastructure, the risk remains if an attacker gains access to a user account. Even if your API is not directly exposed to the internet, any account within the system could potentially be used to exploit this flaw if they have the necessary project permissions.

When should I prioritize fixing this for my systems?

You should begin by locating all active Incus deployments and identifying the system owners responsible for them. Once you have a clear inventory, coordinate with those teams to assess the criticality of the hosted workloads and plan your path to upgrading to version 7.6.0 or later to resolve the authorization flaw.

References