EUVD-2026-57511Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
PR:L confirmed by authenticated LXD user requirement; S:C and full C/I/A reflect host-level code execution via lxc.conf injection from a container-scoped component.
Primary rating from Vendor (canonical).
CVSS VectorVendor: canonical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Lifecycle Timeline
5DescriptionCVE.org
An improper neutralization of special elements vulnerability in LXD's NVIDIA instance configuration handling allows an authenticated attacker to inject arbitrary configuration directives. By supplying newline characters within the 'nvidia.driver.capabilities' or 'nvidia.require.*' configuration values, an attacker can manipulate the generated lxc.conf file. This flaw enables the attacker to execute arbitrary code on the host system with the privileges of the LXD daemon.
Articles & Coverage 1
AnalysisAI
Canonical LXD's NVIDIA GPU passthrough configuration handler fails to sanitize newline characters in user-supplied nvidia.driver.capabilities and nvidia.require.* instance config values, enabling an authenticated attacker to inject arbitrary directives into the generated lxc.conf file. Any LXD user with instance-creation or configuration-modification privileges can exploit this to escape the container boundary and execute arbitrary commands on the host with the full privileges of the LXD daemon - effectively achieving complete host compromise. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the attacker to hold an authenticated LXD identity with at minimum instance-creation or instance-configuration modification privileges - corresponding to PR:L in the CVSS vector (membership in the `lxd` group or equivalent API access). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H scores 8.7 and is well-grounded in the attack mechanics: the LXD API is network-accessible, exploitation requires no special conditions beyond a valid low-privilege LXD identity, and injected `lxc.conf` directives affect the host rather than the container, producing the scope change (S:C) with full C/I/A impact. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An authenticated LXD user with instance-creation rights sets `nvidia.driver.capabilities` to a value such as `compute,utility\nlxc.apparmor.profile=unconfined\nlxc.cap.keep=sys_admin` - embedding newlines to inject additional directives. When LXD generates `lxc.conf` and starts the instance, the LXC runtime processes the injected `lxc.apparmor.profile=unconfined` and capability directives as legitimate configuration, stripping the container's confinement. … |
| Remediation | The primary remediation is to apply the patched LXD release identified in the Canonical security advisory at https://github.com/canonical/lxd/security/advisories/GHSA-vfh7-q59q-54v2. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all LXD deployments and identify instances where non-administrative users have configuration modification capabilities; immediately implement access controls restricting instance configuration and creation privileges to trusted administrators only. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
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
Host root code execution in Canonical LXD arises from a path-traversal flaw in instance template processing, letting an
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 lets an authenticated user with instance-migration privileges smuggle high-privile
Authorization bypass in Canonical LXD lets an authenticated user with copy privileges smuggle instances carrying disallo
Storage quota bypass in Canonical LXD (5.0.x before 5.0.8, 5.21.x before 5.21.6, and 6.0 before 6.10) lets an authentica
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-78 – OS Command Injection
View allSame technique Command Injection
View allVendor StatusVendor
SUSE
Severity: CriticalShare
External POC / Exploit Code
Leaving vuln.today