External risk intelligence

Incus Authorization Bypass Allows Root Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-130784

Incus is a system container and virtual machine manager typically deployed on internal infrastructure or managed via internal APIs. While it may be network-reachable in some administrative environments, it is not designed to be a public-facing service or internet edge gateway, making direct exposure to the public internet uncommon.

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 concerns a critical vulnerability in Incus, a system for managing containers and virtual machines. The issue allows unauthorized clients to bypass security controls, potentially enabling them to create and access resources, or even execute code with root privileges on the host system. Understanding the scope of Incus deployment within the organization is key to assessing potential impact.

  • Bypassed security controls can lead to unauthorized resource access.
  • It could allow code execution on host systems.
  • Confirming Incus usage and exposure is the primary concern.

Attack Path

How an attacker could exploit the issue

An attacker can bypass authorization controls to create or access default project resources within Incus. By setting up bridge networks with raw.dnsmasq directives, attackers can gain root code execution on the host system. They can also manipulate inherited resources using the `?project=` parameter to compromise system integrity.

  • Requires limited client access.
  • Triggers with specific network directives or project parameters.
  • Leads to host root code execution.

Live Threat

Current exploitation, exposure, and threat context

A restricted client could bypass authorization checks to create and access default project resources. This could lead to the execution of arbitrary code as root on the host system or manipulation of inherited resources.

  • Host system or project resources.
  • Bypass authorization checks.
  • Root code execution or resource manipulation.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical authorization bypass vulnerability in Incus affects its entitlement checks, potentially allowing restricted clients to create and access default project resources, execute code as root on the host, or manipulate inherited resources. Real-world response typically falls to platform or infrastructure teams responsible for managing the Incus environment, in coordination with security operations for exposure assessment and application owners if Incus is used to manage application deployments. The immediate first step is to identify all Incus deployments, assess their reachability and business criticality, and then plan remediation or mitigation based on risk.

  • Platform or infrastructure teams should own the issue.
  • Verify Incus reachability and business criticality.
  • Plan remediation based on assessed risk.

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 why is it used?

Incus is a powerful system container and virtual machine manager. It allows administrators to create and maintain isolated environments for applications or entire operating systems on a host server. Users deploy Incus to efficiently manage complex cloud-like infrastructure and resource workloads.

How does CVE-2026-130784 work as an authorization bypass?

This vulnerability falls under the weakness class of Improper Authorization (CWE-863). Essentially, the software fails to properly verify if a user has permission to perform certain actions. By manipulating project parameters, a restricted user can trick the system into granting access to resources or settings they should not be able to reach.

Does this vulnerability trigger automatically?

No. The issue requires specific actions from a user who already has some level of client access to the system. It is not triggered by simply connecting to the software. An attacker must specifically exploit the authorization flaw by crafting requests, such as creating network directives or using specific project parameters to escalate privileges.

Is my Incus deployment at risk according to Halo Surface Signal?

Halo Surface Signal indicates that Incus is typically deployed on internal infrastructure rather than as a public-facing service. Because it is generally not intended to be exposed to the public internet, the likelihood of direct external access is considered low, though you should verify your specific network configuration.

What should I do if I am running Incus?

Your first step is to perform an inventory of all your Incus deployments. Once located, assess their network reachability and business importance. Prioritize evaluating any instances accessible beyond your most trusted internal networks and coordinate with your infrastructure team to plan the necessary updates or security mitigations.

References