External risk intelligence

LXD Btrfs Path Traversal Allows Host File Deletion and Replacement.

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-85526

This vulnerability requires authenticated access with specific instance creation privileges to manipulate LXD backup files. LXD instances and their management interfaces are typically restricted to authorized administrators or internal users within a controlled environment, making direct public internet exposure uncommon.

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 Canonical LXD on Linux, specifically its Btrfs storage driver. It allows an authenticated user with certain privileges to potentially delete or replace important files on the host system. The main concern is confirming if your environment, particularly systems managed by LXD with Btrfs backups, is exposed.

Allows privileged users to manipulate host files.
Matters due to potential unauthorized host system access.
Confirm relevance and exposure; then assess remediation.

Attack Path

How an attacker could exploit the issue

An attacker with the ability to create LXD instances can abuse a path traversal flaw in the Btrfs storage driver. By providing a specially crafted entry within a backup file, an authenticated user can trick the system into deleting or overwriting critical files and directories on the host operating system with root-level privileges.

Authenticated user with instance creation privileges.
Crafted backup import manipulating subvolumes.
Arbitrary file overwrite/deletion on host.

Live Threat

Current exploitation, exposure, and threat context

An authenticated user with instance creation privileges in Canonical LXD on Linux could exploit this vulnerability to delete or replace arbitrary files and directories on the host system with root privileges. This is possible by providing a specially crafted `subvolumes[].path` entry within a `backup/optimized_header.yaml` file during a btrfs optimized backup import.

Host filesystem files and directories.
Via crafted backup import during import.
Arbitrary file deletion or replacement.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects Canonical LXD and allows authenticated users with instance creation privileges to delete or replace arbitrary files on the host filesystem. Responsibility for triage and remediation likely falls to the platform or infrastructure team managing LXD, in coordination with security and system owners. The immediate first step is to identify all LXD instances, confirm their exposure and criticality, and then plan remediation based on risk.

Platform or infrastructure team owns issue.
Verify LXD instance reachability and criticality.
Plan remediation based on identified risks.

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 Canonical LXD and how does it use Btrfs?

Canonical LXD is a system container manager for Linux that provides a lightweight alternative to virtual machines. It uses storage drivers, such as Btrfs, to manage the file systems for these containers. The Btrfs driver specifically enables advanced features like snapshots, cloning, and optimized backups by leveraging the underlying Btrfs file system capabilities on the host.

What is the vulnerability in CVE-2026-85526?

This CVE involves a Path Traversal weakness, categorized as CWE-22. It occurs when software fails to properly sanitize file paths. In this instance, the Btrfs storage driver incorrectly handles input in backup files, allowing a user to navigate outside the intended directory. This flaw grants the ability to overwrite or delete files across the host system with root-level authority.

How can an attacker trigger this LXD flaw?

An attacker must have existing privileges to create LXD instances and initiate a Btrfs optimized backup import. By injecting a malicious path into the subvolumes entry of the backup header, they can trick the driver into accessing host files. It is important to note that standard container operations or general LXD usage that does not involve importing crafted optimized backups will not trigger this specific vulnerability.

Is my system exposed to this threat?

According to Halo Surface Signal, this vulnerability is considered unlikely to be exposed to the public internet. Because the exploit requires authenticated access and specific instance creation privileges, the threat is largely restricted to internal users or administrators already inside your management environment. You should focus your investigation on systems where users have elevated LXD management permissions.

How do I respond to this security issue?

Begin by auditing your infrastructure to locate all instances running Canonical LXD with the Btrfs storage driver. Verify which users or automated processes have the authority to create instances and import backups. Work with your platform team to assess the necessity of these privileges and ensure your LXD software versions are reviewed for official security updates.

References

github.com/canonical/lxd/security/advisories/GHSA-h85r-gjgx-g2rv

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.