A path traversal vulnerability in LXD's instance template processing allows an attacker with container edit permissions, or any user launching a crafted image, to overwrite arbitrary files on the host system as root. When processing target template paths specified in metadata.yaml, LXD validates the path against a confined os.Root directory handle but subsequently opens and creates the file using os.Create with an unconfined string path. This discrepancy between path resolution checks and file creation allows an attacker to escape directory confinement, overwrite root-owned host files, and achieve host root code execution.
Security readout for executives and security teams
Plain-English summary
A flaw in LXD instance templates can let a low-privileged user escape container boundaries and overwrite host files as root. Successful abuse could lead to complete host compromise, service disruption, or data exposure. The risk applies when an attacker can edit containers or launch a crafted image.
Executive priority
Treat as an immediate containment and remediation priority on multi-user or delegated LXD platforms. The possible outcome is full root control of the host, so one compromised tenant or authorized low-privileged account could affect other workloads. Prioritize internet-accessible management planes and systems accepting user-supplied images.
Technical view
LXD validates a template target path using a confined os.Root handle, then creates the file with os.Create using an unconfined string path. Path traversal can therefore escape the intended directory and overwrite root-owned host files, potentially enabling host-root code execution. The record maps this to CWE-22 and CWE-23 and assigns CVSS 3.1 score 9.9.
Likely exposure
Potentially exposed environments are those running the listed LXD versions 4.0.0, 5.0.0, 5.21.0, or 6.0 where users can edit containers or launch untrusted images. The supplied affected-version data is limited and also reports a default status of unaffected, so administrators should confirm exact release status with Canonical.
Exploitation context
The supplied record says exploitation requires container edit permissions or the ability to launch a crafted image; no user interaction is required. It can cross the container-to-host security boundary. The CVE is not identified as KEV, and the supplied sources provide no evidence of active exploitation.
Researcher notes
The security boundary failure is the mismatch between confined validation and unconfined file creation, not merely malformed metadata. Assessment should focus on template-processing call paths, path canonicalization, and whether all file operations remain relative to the confined root. The supplied bundle does not name fixed versions, patches, public proof-of-concept code, or observed attacks.
Mitigation direction
Review Canonical's advisory for fixed releases or vendor-approved remediation.
Upgrade affected LXD installations according to Canonical guidance when a fixed release is identified.
Temporarily restrict container editing and image-launch permissions to trusted administrators.
Prevent untrusted or externally sourced images from being launched pending remediation.
Validation and detection
Inventory LXD installations and compare exact versions with Canonical's advisory.
Identify accounts allowed to edit containers or launch images.
Review recently imported images and instance-template metadata for unexpected target paths.
Investigate unexpected changes to root-owned host files associated with LXD activity.
Confirm remediation using Canonical's stated fixed-version or package guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.