Security readout for executives and security teams
Plain-English summary
A crafted LXD image can abuse a symbolic link to make LXD read or overwrite host files with root privileges. Successful abuse could expose secrets, alter critical files, disrupt services, or enable broader host compromise. The supplied sources identify specific affected LXD releases but do not establish exploitation in the wild or name a fixed release.
Executive priority
Treat this as an immediate exposure-assessment and containment priority, especially on shared or externally managed LXD platforms. Restrict untrusted image operations now, determine whether listed releases are deployed, and obtain Canonical's confirmed remediation. Host-level root file access makes potential impact severe even though active exploitation is not established.
Technical view
During image import or unpacking, affected LXD versions do not verify whether metadata.yaml is a symbolic link. A crafted archive can redirect privileged file operations to host paths, producing arbitrary host file read and write. The CVSS 3.1 score is 9.9, with network reachability, low complexity, low privileges, no user interaction, and changed scope.
Likely exposure
Exposure is highest where low-privileged or untrusted users can submit or trigger LXD image imports or unpacking. The bundle lists LXD 4.0.0, 5.0.0, 5.21.0, and 6.0 as affected, with other versions defaulting to unaffected. Deployment configuration and backported vendor fixes still require verification.
Exploitation context
The vulnerability requires a crafted image archive containing a symlinked metadata.yaml targeting a host path. The CVSS vector indicates low privileges and network accessibility, but the precise required LXD permissions are not documented in the bundle. CISA KEV listing is false, and no supplied source reports active exploitation.
Researcher notes
This is CWE-59 link-following behavior at a privileged archive boundary. Investigation should focus on metadata.yaml type validation, archive extraction paths, authorization around import operations, and host-file integrity after imports. The supplied evidence does not identify fixed versions, affected package revisions, indicators of compromise, public proof-of-concept availability, or confirmed attacks.
Mitigation direction
- Restrict image import and unpacking capabilities to trusted administrators.
- Do not accept image archives from untrusted or unverified sources.
- Check Canonical's advisory for fixed versions or backported package status.
- Apply Canonical's remediation guidance promptly when confirmed.
- Monitor privileged LXD operations and unexpected host-file changes.
Validation and detection
- Inventory LXD versions and compare them with the listed affected releases.
- Identify users and services permitted to import or unpack images.
- Review recent image sources and import activity for untrusted archives.
- Inspect suspect archives safely for a symlinked metadata.yaml entry.
- Verify installed package remediation status against Canonical's advisory.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-59: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
Open ATT&CK lookupFile access behavior lookup
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.
Open ATT&CK lookupCVE-2026-63293 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16canonicalVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/canonical/lxd/security/advisories/GHSA-j825-cg34-5fr5CVE reference, canonical · vdb-entry, vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Link Resolution Before File Access ('Link Following')
Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.