External risk intelligence

Incus Arbitrary File Write Vulnerability Leads to Root Command Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-48769

The vulnerability exists in the Incus client, which is typically used by administrators or developers to manage local or internal container/VM infrastructure. While it involves interaction with an image server, the client itself is not a public-facing service, and intentional exposure of the client-side management interface to the public internet is not a standard or required deployment pattern.

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 vulnerability in the Incus client, a system for managing containers and virtual machines, could allow an attacker to execute arbitrary commands as root on the server. This issue arises when the client interacts with a malicious image server that provides a specially crafted header. While the vulnerability is critical, its potential impact is primarily within environments where the Incus client is directly exposed to untrusted image sources.

  • A flaw allows unauthorized command execution.
  • Critical vulnerability in container management software.
  • Assess relevance to your managed environments.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user running the Incus client into connecting to a specially crafted image server. This server would send back a malicious response, allowing the attacker to write files anywhere on the user's system, potentially leading to full control as the root user.

  • Entry Condition: User connects to a malicious image server.
  • Trigger Point: Client receives a crafted header.
  • Resulting Risk: Arbitrary file write, leading to root code execution.

Live Threat

Current exploitation, exposure, and threat context

A vulnerability in the Incus client could allow an attacker to execute arbitrary commands as root on the server when a malicious image server responds with a specially crafted `Incus-Image-Hash` header. This could affect the integrity and availability of the server, as well as any data managed by Incus.

  • Arbitrary file writes on the server.
  • Malicious image server response.
  • Root command execution on the server.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the Incus client impacts teams responsible for managing container and virtual machine infrastructure. The first step is to identify all Incus client instances, determine their exposure and criticality, and locate the accountable owner to initiate a risk-based remediation plan.

  • Infrastructure or Platform teams should own the issue.
  • Verify Incus client reachability and asset criticality.
  • Plan remediation based on asset risk exposure.

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

Incus is an open-source system container and virtual machine manager. It provides a unified platform for administrators and developers to deploy, manage, and scale Linux-based virtual environments and system containers, acting as a high-level tool for orchestration and lifecycle management of these computing resources.

How does CVE-2026-48769 allow code execution?

This vulnerability is classified under CWE-20, which relates to improper input validation. In the Incus client, the software fails to properly validate the 'Incus-Image-Hash' header received from an image server. An attacker can exploit this to perform an arbitrary file write, effectively writing files to unintended locations on the system, which can result in executing commands with root privileges.

When does this vulnerability trigger?

The flaw is triggered specifically when a user instructs the Incus client to connect to a malicious or compromised image server that returns a crafted hash header. Simply running the Incus software locally or connecting to trusted, internal image servers does not trigger the vulnerability.

Is my environment at risk from this flaw?

According to Halo Surface Signal, this risk is categorized as unlikely because the Incus client is primarily a management tool used by staff, not a public-facing service. The risk is highest if your infrastructure is configured to pull images from untrusted or public sources, as the client's management interface is generally not intended to be exposed to the public internet.

What steps should I take to address this?

Start by identifying all systems running the Incus client in your environment. Once you have an inventory, prioritize patching instances that frequently interact with external or third-party image repositories. You should coordinate with your infrastructure or platform teams to update to version 7.2.0 or later to ensure the malicious header validation issue is resolved.

References