External risk intelligence

Incus Configuration Injection Leads to Host Command Execution

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-130786

Incus is a system container manager typically managed by authenticated local users or internal administrators rather than being exposed directly to the public internet. While it can be networked, its core function is infrastructure management, which is generally restricted to internal control planes or specific management interfaces behind firewalls, making public internet exposure 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

A critical vulnerability exists in Incus, affecting how it handles user-provided image data. This flaw could allow attackers with limited access to execute commands with root privileges on the host system, potentially impacting sensitive data and operations. The main concern is confirming whether this technology is in use and potentially exposed.

  • Insecure configuration handling can lead to root access.
  • Critical flaw impacts container management systems.
  • Confirm relevance and exposure for this system.

Attack Path

How an attacker could exploit the issue

An attacker who can launch instances from controlled images can manipulate Incus's configuration to inject malicious commands. This is achieved by embedding line breaks within specific configuration values, allowing the attacker to add unauthorized hooks or mount points. When the vulnerable component processes these crafted configurations, it can lead to the execution of arbitrary code with root privileges on the host system or unauthorized access to host file paths.

  • Requires ability to launch instances.
  • Injects directives via crafted image configurations.
  • Risk of root command execution or host path access.

Live Threat

Current exploitation, exposure, and threat context

Users who can launch instances from controlled images could leverage this vulnerability to inject directives into LXC configurations. This could allow them to execute commands as root on the host system or mount host paths, even within restricted projects.

  • Host system commands could be executed.
  • Crafted images could trigger malicious behavior.
  • Unauthorized root access may be gained.

Operational Fix

Recommended remediation, mitigation, and detection steps

The platform or infrastructure team managing Incus deployments is likely responsible for addressing this vulnerability. The first practical step involves identifying all Incus instances, determining their business criticality and external reachability, and then locating the accountable system owner to plan remediation.

  • Platform team owns Incus instances.
  • Verify instance reachability and criticality.
  • Plan and coordinate remediation actions.

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 system container manager used to run and manage isolated environments, often referred to as system containers or virtual machines. Developers and system administrators use it to deploy infrastructure, isolate applications, and maintain controlled environments that share a host system's kernel while remaining distinct from one another.

What is the CVE-2026-130786 vulnerability?

This is a configuration injection flaw, categorized as CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component). It occurs when the software incorrectly handles user-supplied data in container configuration files. By embedding malicious line breaks, an attacker can trick the system into processing unauthorized commands, effectively breaking out of the container's isolation to run actions with root privileges on the host.

How is this configuration injection triggered?

The vulnerability is triggered when a user who has permission to launch instances uses a specially crafted container image. By injecting specific line breaks into OCI configuration fields, the attacker can force the host to execute unintended instructions. Simply viewing or managing existing containers without the ability to launch new instances from controlled images does not trigger this flaw.

Is my Incus deployment at high risk?

According to Halo Surface Signal, Incus is typically used for internal infrastructure management, making direct public exposure uncommon. However, you should evaluate if your specific installation is accessible from outside your private network. If your management interface is reachable over the internet or if untrusted users have permission to launch instances, your risk level increases significantly.

What should I do first to address this?

Begin by identifying all Incus instances within your environment and mapping which teams are responsible for managing them. Assess the reachability and business criticality of each instance to prioritize your efforts. Once identified, work with the relevant system owners to schedule the necessary software updates to move beyond the affected versions.

References