CVE-2026-63295 Canonical CVE debrief

Who should care

Defenders responsible for LXD deployments, particularly those with restricted container privileges, should assess exposure and verify instance configurations to prevent potential authorization bypass.

Why it matters

Defenders should prioritize verifying and updating LXD instances to ensure proper enforcement of security constraints, particularly in environments where container privileges are restricted. The vulnerability allows an authenticated attacker to bypass project-level container isolation restrictions, potentially leading to unauthorized access or data breaches. Evidence is limited, and specific details on exploitation are not provided, emphasizing the need for caution and thorough verification.

• Potential bypass of project-level container isolation restrictions
• Possible unauthorized access to sensitive data or systems
• Need for verification of LXD instance configurations
• Priority for updating LXD to patched versions

Technical summary

The vulnerability occurs when LXD fails to enforce project-level container isolation restrictions if an instance configuration omits the security.idmap.isolated key. An authenticated attacker can exploit this flaw by creating or updating an instance without explicitly setting security.idmap.isolated, bypassing the target project's security constraints. This allows unauthorized access or potential data breaches in environments where container privileges are restricted. Evidence is limited, emphasizing the need for caution and thorough verification of LXD instance configurations.

Defensive priority

Defenders should prioritize verifying and updating LXD instances to ensure proper enforcement of security constraints, particularly in environments where container privileges are restricted.

Recommended defensive actions

• Verify LXD instance configurations to ensure security.idmap.isolated key is properly set
• Update LXD to version 4.0.13, 5.0.9, 5.21.7, or 6.11
• Review project-level container isolation restrictions and adjust as necessary
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The CVE record and NVD entry provide details on the authorization bypass vulnerability in LXD. Vendor advisories and exploit information are available, but specific details on exploitation are limited.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.