External risk intelligence

Incus Arbitrary File Read Create Write Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-48749

Incus is a container and virtual machine manager typically deployed on internal infrastructure, developer workstations, or private server environments. While it manages containers, it is not designed as a public-facing internet service or edge gateway, and its management interfaces are generally protected by internal network controls.

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 system for managing containers and virtual machines. The issue, if exploited, could allow unauthorized access to read or write files on the host system, potentially leading to the execution of arbitrary commands. While the technology is typically used in internal environments, confirming its presence and exposure is prudent to ensure business continuity and data integrity.

  • Malicious images could access host files.
  • Confirms exposure and relevance of this issue.
  • Understand potential impact on internal systems.

Attack Path

How an attacker could exploit the issue

An attacker with limited privileges could leverage a specially crafted image to gain unauthorized access to the host system. This vulnerability in Incus, a container and virtual machine manager, could allow an attacker to read or write arbitrary files on the host, potentially leading to the execution of commands.

  • Requires limited privileges.
  • Triggered by a specially crafted image.
  • Allows host file access and command execution.

Live Threat

Current exploitation, exposure, and threat context

A specially crafted image, when used with Incus, could allow an authenticated user to read or write arbitrary files on the host system. This might enable an attacker to execute commands on the host when supported by the advisory.

  • Host file system integrity.
  • Malicious image ingestion.
  • Arbitrary command execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-World Ownership The use of Incus, a system container and virtual machine manager, suggests that platform or infrastructure teams are most likely responsible for its operation. Given the critical nature of this vulnerability, the first step is to identify all instances of Incus, assess their exposure and business criticality, and then coordinate with the relevant application or system owners to plan remediation.

  • Platform or Infrastructure teams should own.
  • Verify Incus instances and exposure.
  • Plan risk-based 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 how is it used?

Incus is an open-source tool used to manage system containers and virtual machines. It allows users to run multiple isolated operating system environments on a single host. It is commonly deployed by infrastructure teams and developers to create portable, lightweight computing environments for applications.

What is the vulnerability in CVE-2026-48749?

This vulnerability is classified as CWE-73, which involves external control of file name or path. In Incus, it means the software does not properly validate file paths provided by container images. This flaw allows a user to escape the expected container boundaries to read, create, or modify arbitrary files on the host machine, which can subsequently be leveraged to run unauthorized commands.

How is this Incus vulnerability triggered?

An attacker triggers this issue by introducing a specially crafted container image into the environment. Simply having the software installed does not trigger the bug; it requires the processing or ingestion of a malicious image. Operations performed with trusted, standard images do not initiate this unauthorized file access.

Do I need to worry if my Incus instance is internal?

According to Halo Surface Signal, this software is typically found on private servers or developer workstations rather than being public-facing. While the vulnerability is technically network-accessible, the risk is lower for isolated systems. You should focus on instances that have any connectivity to untrusted networks or multi-user environments where malicious image ingestion is possible.

How should I respond to this threat?

First, perform an inventory to locate all active Incus installations across your infrastructure. Once identified, prioritize updating to version 7.2.0, which contains the official fix for this flaw. If immediate patching is not feasible, restrict who is permitted to upload or manage container images to prevent the use of malicious files.

References