External risk intelligence

LXD Instance Migration Authorization Bypass Allows High-Privilege Configuration Evasion.

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-63296

LXD is a system container manager typically managed by administrators or within internal infrastructure. While it may be network-accessible in specific cloud or multi-tenant environments, it is generally not exposed directly to the public internet, and exploitation requires prior authentication.

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 in LXD allows authenticated users to bypass project security settings when moving system instances. An attacker could exploit this to place instances with unauthorized high-privilege configurations into restricted projects, undermining existing security controls. The primary concern is confirming if this technology is in use and if it is exposed.

Attackers can move restricted instances to new projects.
Bypasses security controls for moving instances.
Confirm relevance and exposure within your environment.

Attack Path

How an attacker could exploit the issue

An attacker with authenticated access to LXD can exploit this flaw by migrating a virtual instance to a new project. During this migration, the system fails to properly check the instance's configuration against the target project's security rules. This allows the attacker to bypass project restrictions and move an instance with potentially unsafe, high-privilege settings into a project that should not permit such configurations.

Authenticated access to LXD required.
Instance migration with configuration overrides triggers vulnerability.
Bypasses project security for high-privilege configurations.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an authenticated attacker to bypass project restrictions when migrating LXD instances. By providing configuration overrides during migration, an attacker could move instances with high-privilege configurations into projects where those configurations are normally disallowed, circumventing existing security controls.

Restricted project configurations.
Migration with configuration overrides.
Bypassing security controls.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts LXD, a system container manager often managed by infrastructure or platform teams. The first practical step is to identify all LXD deployments, confirm if they are internet-facing or critical, and then locate the system owners responsible for these deployments to initiate a risk-based remediation plan.

Infrastructure or platform teams own the issue.
Verify LXD instance migration reachability.
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 LXD and how is it used?

LXD is a powerful system container manager that provides a comprehensive experience for managing Linux containers and virtual machines. It is widely used by infrastructure and platform teams to build scalable, isolated environments. By offering advanced features like hardware passthrough, snapshotting, and live migration, it allows organizations to run complex workloads with near-native performance while maintaining distinct boundaries between different project resources.

What does CWE-863 mean for CVE-2026-63296?

CWE-863, or Incorrect Authorization, occurs when software does not perform sufficient checks to ensure that an actor is allowed to perform a specific action. In the context of CVE-2026-63296, this means that while the system verifies you have permission to initiate an instance migration, it fails to verify that the instance's final configuration complies with the security policies defined for the destination project.

How does an attacker trigger this LXD vulnerability?

The flaw is triggered during the migration of a container or virtual instance between projects when the user includes configuration overrides. It is not triggered by standard operations that do not involve moving instances or modifying their settings during transit. Successful exploitation requires the attacker to already have authenticated access to the LXD environment.

Is my environment at risk according to Halo Surface Signal?

Halo Surface Signal notes that while LXD is a critical tool for infrastructure management, it is typically restricted to internal networks rather than being directly exposed to the public internet. Because the vulnerability requires an attacker to be authenticated first, the risk is generally lower for systems that are not accessible to untrusted users.

What are the first steps to address CVE-2026-63296?

Start by identifying all LXD installations within your environment. Once you have a complete inventory, verify whether these instances are accessible over a network or restricted to internal traffic. Coordinate with the teams responsible for these systems to evaluate their current configurations and prioritize a risk-based remediation plan to protect your project boundaries.

References

github.com/canonical/lxd/security/advisories/GHSA-gcr9-5q6r-w625

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.