Summary
A critical authorization bypass in LXD allows an authenticated attacker to circumvent target project restrictions during instance migration.
By supplying configuration overrides that are not rechecked against the destination project's policies, an attacker may move an instance with disallowed high-privilege settings into a restricted project.
Affected context
The vulnerability occurs in LXD deployments that support instance migration between projects and apply security restrictions to destination projects. It becomes risky when migration configuration overrides are accepted without validating the resulting instance configuration against the target project's enforced policies.
Exploit preconditions
- Attack surface: LXD instance migration functionality
- Required access: An authenticated LXD user permitted to initiate or influence instance migration
- Trigger point: Migration of an instance into a target project with enforced restrictions
- Why exploitation is possible: Configuration overrides are accepted without a complete authorization check against the destination project's restrictions
Why this happens
The underlying issue is an incomplete authorization decision during instance migration. LXD validates migration-related configuration without ensuring that the final instance configuration complies with the target project's security restrictions.
This maps to CWE-863: Incorrect Authorization, where an authenticated principal is allowed to perform an operation or establish a resource state that should have been denied by the applicable access-control policy.
Potential impact
- An attacker may bypass target project restrictions
- Instances with disallowed high-privilege configurations could enter restricted projects
- Project isolation controls may be weakened
- Attackers could gain access to capabilities or resources unavailable under normal policy enforcement
- Administrative and tenant security boundaries could be compromised
General mitigation guidance
Mitigation generally focuses on making authorization decisions against the complete post-migration configuration.
Common defensive patterns include:
- Revalidating every effective configuration value against the destination project's restrictions
- Applying authorization checks after overrides are merged and before migration is committed
- Denying unknown, privileged, or policy-sensitive overrides by default
- Enforcing least-privilege permissions for accounts allowed to migrate instances
- Separating migration authorization from ordinary instance-management permissions
- Auditing migration requests and policy-denial events
These controls reduce reliance on the source configuration and help preserve project isolation.
How teams detect issues like this
Organizations can identify similar authorization flaws through:
- Static analysis and code review of migration paths, override handling, and policy checks
- Tests that attempt to move restricted configurations across project boundaries
- Review of whether authorization is evaluated on the final effective resource state
- Policy enforcement that blocks privileged instance settings in restricted projects
- Audit monitoring for migrations involving denied settings, unusual project transitions, or unexpected privilege changes
Automated security review tools may help flag missing authorization checks, but business-logic testing remains important.

