External risk intelligence

LXD Path Traversal Leading to Host Root Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-66897

LXD is a system container manager typically restricted to internal infrastructure, administrative networks, or private cloud environments. While network-reachable in some configurations, it is not designed to be exposed directly to the public internet, and requires specific, uncommon, or misconfigured setups to be reachable by external attackers.

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 vulnerability affects LXD, a system container manager, allowing an attacker with specific permissions or by launching a specially crafted image to overwrite critical files on the host system with root-level access. This could potentially lead to the execution of arbitrary code on the host. The main concern is confirming if our environment utilizes LXD and is exposed to this type of attack.

Allows unauthorized file overwrites on host systems.
Critical for confirming LXD's presence and exposure.
Assess LXD usage and potential impact on host systems.

Attack Path

How an attacker could exploit the issue

An attacker with the ability to edit LXD containers or launch specially crafted images can exploit a path traversal flaw to overwrite any file on the host system with root privileges. This happens because LXD initially checks file paths within a restricted directory but then uses an unvalidated string to create the file, allowing the attacker to break out of confinement and execute code on the host.

Requires container edit permission or launching a crafted image.
Attackers can overwrite host files via template metadata.
Leads to host root code execution.

Live Threat

Current exploitation, exposure, and threat context

A path traversal vulnerability in LXD's instance template processing could allow an attacker with specific permissions or by launching a crafted image to overwrite arbitrary files on the host system as root. This occurs when LXD processes template paths, and a discrepancy between path validation and file creation allows an attacker to bypass directory restrictions, potentially leading to host root code execution.

Host system files.
Unrestricted file creation after path validation.
Host root code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in LXD's instance template processing impacts hosts where LXD is deployed and allows attackers with container edit permissions or those launching crafted images to achieve root code execution on the host system. System owners and infrastructure teams should first identify all LXD deployments, assess their reachability and criticality, and then coordinate with the platform or security teams for remediation.

Identify LXD deployment scope.
Verify host system exposure and criticality.
Plan remediation with platform teams.

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 developed by Canonical. It allows administrators to run and manage full Linux systems within lightweight, isolated environments. It is commonly used to build private cloud infrastructure, host scalable microservices, and manage compute resources efficiently by sharing the host system's kernel while keeping the user-space environments separate.

What does CVE-2026-66897 mean by path traversal?

This vulnerability is classified as CWE-22, which is improper limitation of a pathname to a restricted directory. In LXD, the software tries to lock file operations to a specific safe folder. However, a mismatch in how the software validates the file path versus how it actually creates the file allows an attacker to 'traverse' or step outside that folder. This lets them write files anywhere on the host system.

How is this vulnerability triggered in LXD?

An attacker triggers this by providing a crafted image or manipulating instance template metadata. The flaw is not triggered by standard container usage. It requires the ability to define target paths that the system then processes incorrectly. If a user does not have permission to edit containers or launch new images, they cannot initiate the sequence that leads to the restricted path escape.

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

According to Halo Surface Signal, this is less likely to be a high-risk scenario for most users. LXD is designed for private clouds and administrative networks, not for public exposure. Because it is usually kept off the internet, an attacker typically needs existing internal network access to reach the service. You should prioritize this if your configuration deviates from these standard, restricted setups.

When should I take action for this CVE?

You should begin by cataloging all servers running LXD to determine your total footprint. Once identified, evaluate which containers have users with image-creation or container-edit permissions. Coordinate with your platform teams to restrict these privileges while verifying that your host systems are not directly reachable from untrusted networks, and prepare to apply patches as they become available.

References

github.com/canonical/lxd/security/advisories/GHSA-q39m-8fx9-42fv

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.