External risk intelligence

LXD Root Command Execution via Malicious Archive Symlink

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-63294

LXD is a system container manager typically deployed in internal infrastructure or controlled environments for virtualization and management. While it interacts with archives and images, these operations generally occur within internal administrative or build workflows rather than as public-facing internet services.

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 security vulnerability has been identified in LXD, a system container manager, that could allow an attacker to gain root command execution on the host system. This is due to improper handling of symbolic links within image or backup archives, potentially enabling the execution of arbitrary commands with root privileges if a malicious archive is processed.

An issue allows root control via crafted archives.
This could compromise host systems with LXD.
Confirm LXD relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by submitting a specially crafted archive file to a system running LXD. If LXD processes this archive and encounters a symbolic link named `backup.yaml` within it, the system may execute arbitrary commands with root privileges due to insufficient validation of the configuration metadata. This could allow an attacker to take full control of the host system.

Requires unauthenticated network access.
Triggered by importing a crafted archive.
Results in root command execution.

Live Threat

Current exploitation, exposure, and threat context

When LXD incorrectly processes a maliciously crafted archive containing a symbolic link to a backup.yaml file, it can lead to the execution of arbitrary commands with root privileges on the host system. This could potentially impact the integrity and availability of the host system and any data managed by LXD.

Host system commands and configuration could be affected.
Via crafted archives and symlinked files.
Unauthorized root-level system access and control.

Operational Fix

Recommended remediation, mitigation, and detection steps

The described vulnerability in LXD, allowing root command execution via crafted archives, likely impacts infrastructure or platform teams responsible for container management. The immediate practical step is to identify all LXD deployments, assess their exposure and criticality, and determine the accountable owner for remediation planning.

Identify LXD deployments and owners.
Verify reachability and business criticality.
Plan remediation based on assessed risk.

Supplementary metadata

CVSS vector

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.

Free EASM Trial See How Signal Works

Frequently asked questions

What is LXD and what is it used for?

LXD is a system container manager that provides a platform for running and managing isolated Linux environments. It is frequently used by infrastructure and platform teams to perform virtualization, manage container lifecycles, and handle image or backup distributions across host systems.

What does CVE-2026-63294 mean for security?

This vulnerability is classified as CWE-59, which involves the improper handling of symbolic links. In this case, LXD fails to validate or confine a 'backup.yaml' file when it is presented as a symbolic link within an archive. This weakness allows an attacker to bypass security restrictions, leading to arbitrary command execution with elevated root privileges on the underlying host.

How is this LXD vulnerability triggered?

The flaw is triggered when LXD imports or unpacks a specially crafted image or backup archive containing a malicious symbolic link named 'backup.yaml'. It is important to note that simply having LXD installed or running a container does not trigger the bug; the system must specifically process a malicious archive that leverages this symlink path.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal notes that LXD is typically deployed in internal infrastructure or controlled environments rather than as public-facing services. Because these archive operations usually occur within private administrative or build workflows, the likelihood of remote exploitation via the internet is generally considered low, though internal access remains a factor.

Do I need to take action if I run LXD?

Yes, you should begin by creating an inventory of all LXD deployments within your environment. Once identified, assess the criticality of these systems and determine who is responsible for their maintenance. This information will help you prioritize remediation planning and verify the business impact of these specific container management hosts.

References

github.com/canonical/lxd/security/advisories/GHSA-fv82-v4fj-mm4m

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.