EUVD-2026-57516Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Bypass enables unauthorized privileged container state (I:L); no confidentiality or availability impact described; authenticated project member required (PR:L).
Primary rating from Vendor (canonical).
CVSS VectorVendor: canonical
Lifecycle Timeline
2DescriptionCVE.org
An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass project-level container isolation restrictions. When a project is configured with restrictions on container privileges (such as enforcing restricted.containers.privilege=isolated), LXD fails to enforce the requirement if an instance configuration omits the security.idmap.isolated key. An attacker can exploit this flaw by creating or updating an instance without explicitly setting security.idmap.isolated, bypassing the target project's security constraints.
AnalysisAI
Authorization bypass in LXD (Canonical) allows authenticated project members to circumvent container privilege isolation restrictions enforced at the project level. When a project is configured with restricted.containers.privilege=isolated, LXD's enforcement logic fails to apply the restriction if an instance is created or updated without explicitly setting the security.idmap.isolated key - effectively treating omission as permission. No public exploit code or CISA KEV listing exists at time of analysis, but the bypass is exploitable by any authenticated LXD user with instance-creation rights in a restricted project.
Technical ContextAI
LXD is Canonical's system container and virtual machine manager, widely used in Ubuntu-based infrastructure. Projects in LXD support resource and security restriction policies; restricted.containers.privilege=isolated is a project-level control intended to mandate that all containers use isolated UID/GID mappings via security.idmap.isolated, preventing privilege escalation out of container namespaces. The flaw (CWE-863: Incorrect Authorization) is a logic gap in LXD's restriction enforcement: the check evaluates whether security.idmap.isolated is set to a disallowed value, but does not account for the key being entirely absent from the instance configuration. The affected product is cpe:2.3:a:canonical:lxd:*:*:*:*:*:*:*:* - all versions per NVD CPE. The advisory is published by Canonical at GHSA-7vp9-3vmp-c5jm.
RemediationAI
Upgrade LXD to the patched version referenced in the Canonical security advisory at https://github.com/canonical/lxd/security/advisories/GHSA-7vp9-3vmp-c5jm - the exact fixed release version is not independently confirmed from available data and must be verified in the advisory. As a compensating control prior to patching, administrators should audit all existing instance configurations within restricted projects to ensure security.idmap.isolated is explicitly set to true on every instance, rather than relying on the project-level restriction alone. Additionally, LXD project membership and instance-creation rights should be restricted to trusted users only, since the bypass requires authenticated access (PR:L). Note that explicit instance-level key enforcement adds per-instance administrative overhead and may conflict with automation pipelines that rely on project-level policy inheritance.
Cross-Site Request Forgery (CSRF) in LXD-UI in Canonical LXD versions >= 5.0 on Linux allows an attacker to create and s
Privilege Escalation in operations API in Canonical LXD <6.5 on multiple platforms allows attacker with read permissions
Information Spoofing in devLXD Server in Canonical LXD versions 4.0 and above on Linux container platforms allows attack
Path Traversal in the log file retrieval function in Canonical LXD 5.0 LTS on Linux allows authenticated remote attacker
A arbitrary file access vulnerability (CVSS 6.5) that allows an attacker with instance configuration permissions. Risk
Privilege escalation to host root in Canonical LXD occurs when the container manager unpacks crafted image or backup arc
Host root code execution in Canonical LXD arises from a path-traversal flaw in instance template processing, letting an
Arbitrary host file read and write in Canonical LXD occurs because the image import/unpack routine does not verify wheth
Canonical LXD's NVIDIA GPU passthrough configuration handler fails to sanitize newline characters in user-supplied `nvid
Path traversal in Canonical's LXD container and VM manager allows a user with backup import/restore privileges to write
Authorization bypass in Canonical LXD (6.0 before 6.10, 5.21.x before 5.21.6, 5.0.x before 5.0.8) lets an authenticated
Project-confinement bypass in Canonical LXD lets an authenticated user holding can_create_instances on a restricted proj
Same weakness CWE-863 – Incorrect Authorization
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: ModerateShare
External POC / Exploit Code
Leaving vuln.today