External risk intelligence

Incus Path Traversal Vulnerability Affects Migration Peers

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-130780

Incus migration endpoints typically operate within internal, trusted infrastructure environments between specific container hosts. While migration traffic can technically traverse networks, it is not a service designed for public internet exposure, and common deployment patterns involve isolated control plane networks or secure peering rather than direct exposure to the public internet.

Path Traversal

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 details a path traversal vulnerability affecting Incus, a technology used for container management. The flaw allows unauthorized manipulation of files on hosts, potentially leading to system compromise or disruption by maliciously crafted migration requests. Understanding this vulnerability is important for assessing potential risks to our containerized environments.

  • Malicious migration requests can write files anywhere.
  • Impacts systems managing containers with direct storage access.
  • Confirm relevance and exposure of our Incus deployments.

Attack Path

How an attacker could exploit the issue

An attacker who controls a migration source can exploit this vulnerability by sending specially crafted migration offer headers. This allows them to write files to arbitrary locations on the host system, potentially leading to host compromise, denial of service, or bypassing access controls.

  • Requires control of a migration source.
  • Triggered by unvalidated names in migration headers.
  • Risk of arbitrary file writes and host compromise.

Live Threat

Current exploitation, exposure, and threat context

A path traversal vulnerability in Incus could allow a malicious migration peer to write arbitrary root-owned files to the host system when using dir storage pools. This may occur if an attacker controls a migration source and can manipulate unvalidated volume and snapshot names in the migration offer header.

  • Arbitrary host files.
  • Unvalidated migration data.
  • Host system compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

The security of Incus systems relies on application owners and infrastructure teams to manage migration peer configurations and storage pool access. The immediate first step is to inventory all Incus instances, confirm exposure and criticality, and identify the accountable owner for each. Subsequent actions, including remediation planning, will depend on this initial assessment.

  • Verify Incus instance inventory and exposure.
  • Identify accountable owners for each instance.
  • 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 an open-source system used to manage containers and virtual machines. It provides tools for infrastructure teams to oversee system resources, handle storage, and facilitate the movement of containerized workloads between different host servers.

How does CVE-2026-130780 work?

This vulnerability is a path traversal flaw (CWE-22). It occurs when the software fails to properly sanitize names for volumes or snapshots during a migration process. A malicious migration source can exploit this to trick the system into writing files to unintended locations on the host, rather than restricting operations to specific storage directories.

What triggers this vulnerability?

The issue is triggered when a migration source sends a specifically crafted migration offer header containing malicious volume or snapshot names. It is important to note that migration processes that do not involve the 'dir' storage pool type are not subject to this specific file-write manipulation.

Is my Incus deployment at risk?

Halo Surface Signal indicates that Incus migration endpoints are typically used within internal, trusted infrastructure and are not meant for public exposure. Your risk depends on whether your migration peers are strictly controlled; if you allow migration from untrusted or unauthorized sources, the potential for host compromise significantly increases.

How do I respond to this threat?

Start by auditing your infrastructure to identify all active Incus instances and their migration configurations. Determine which instances are authorized to perform migrations and confirm the identity of the owners for these systems. Once you have a clear inventory, prioritize verifying that your migration peers are restricted to trusted, internal networks while planning for updates to secure the software.

References