External risk intelligence

Canonical LXD Root Filesystem Write Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-87799

LXD migration endpoints are typically restricted to internal infrastructure management networks between trusted hosts. While network-reachable in some specific cluster environments, they are not intended for public internet exposure and are generally protected by internal network controls and authentication requirements.

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 vulnerability has been identified in Canonical LXD, a system used for managing Linux containers and virtual machines. The flaw could allow an authenticated user or a malicious migration source to gain complete control of the host system by writing files to arbitrary locations. This could lead to a full compromise of the host.

An attacker can gain full host control.
It impacts systems managing Linux containers.
Confirm relevance and exposure within your LXD environments.

Attack Path

How an attacker could exploit the issue

An attacker with existing access to create LXD instances or storage within a project, or by controlling a migration source, can leverage an improper link resolution flaw during data migration. By sending a specially crafted data stream, the attacker can trick the system into writing malicious files to any location on the host system with root privileges, potentially leading to complete system takeover.

Requires authenticated client or migration source.
Triggered by crafted migration data stream.
Risk of full host compromise.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an authenticated user or a malicious migration source to write arbitrary files to the host system as root. This could occur when migrating instances or custom storage volumes, using specially crafted rsync or btrfs send streams to plant and write through a symbolic link.

Arbitrary file write on host system.
Crafted rsync/btrfs streams during migration.
Potential for full host compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

In real-world scenarios, platform and infrastructure teams responsible for Canonical LXD deployments should lead the remediation efforts. The immediate first step involves identifying all LXD instances, assessing their network reachability and business criticality, and pinpointing the accountable owner for each. Subsequent planning for remediation should be risk-based.

Platform/Infrastructure teams own the issue.
Verify LXD instance reachability and criticality.
Plan remediation based on identified 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 Canonical LXD?

Canonical LXD is a system-level container manager for Linux. It is used by administrators to manage the lifecycles of containers and virtual machines, providing an environment that acts like a lightweight virtualized operating system. It relies on features like migration to move instances or storage volumes between different host servers in a cluster.

What does CVE-2026-87799 mean for system security?

This vulnerability is classified as improper link resolution (CWE-59). It means the software fails to correctly handle symbolic links during the migration process. An attacker can use these links to trick the system into writing files outside of intended directories, eventually overwriting critical system files with root-level permissions.

How is this vulnerability triggered?

It occurs during the migration of instances or storage volumes. An attacker must send a specially crafted rsync or btrfs data stream that contains a malicious symbolic link. Normal operations that do not involve transferring data via these migration paths or using untrusted migration sources do not trigger the flaw.

Is my system at risk if it is not on the public internet?

According to Halo Surface Signal, this vulnerability is unlikely to be reachable from the public internet. LXD migration endpoints are typically restricted to internal management networks between trusted hosts. You are generally at lower risk if your environment is protected by internal network controls and requires authentication for migration.

What steps should I take to respond to this?

Your first step is to identify all running LXD instances within your infrastructure and confirm their current software version. Verify which instances are involved in migration workflows and ensure that access to migration endpoints is strictly controlled. Coordinate with your platform or infrastructure team to plan a transition to patched versions (4.0.14, 5.0.10, 5.21.8, or 6.10 and later).

References

github.com/canonical/lxd/security/advisories/GHSA-fmc3-3cpq-6whr

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.