Security readout for executives and security teams
Plain-English summary
LXD can be tricked into following a symbolic link inside a crafted image or backup archive. When LXD imports or unpacks that archive, attacker-controlled configuration may escape expected confinement and run commands as root on the host. Successful exploitation could compromise the host and its workloads.
Executive priority
Treat exposed or multi-user LXD environments as an immediate remediation priority because successful exploitation grants root control of the host. Prioritize systems accepting remote archive imports, restrict that capability now, and schedule vendor-directed upgrades. Evidence of active exploitation is not established.
Technical view
CVE-2026-63294 is a CWE-59 link-following flaw involving backup.yaml during LXD archive import or unpacking. Insufficient symlink validation allows unconfined configuration metadata to be processed, enabling root command execution. The supplied CVSS 3.1 score is 9.9 with network access, low complexity, low privileges, no user interaction, and changed scope.
Likely exposure
Exposure is most likely where listed LXD versions—4.0.0, 5.0.0, 5.21.0, or 6.0—accept image or backup archives from low-privileged or otherwise untrusted users. The bundle marks other versions unaffected by default, but administrators should confirm exact release boundaries with Canonical's advisory.
Exploitation context
The supplied record does not show CISA KEV listing or provide evidence of active exploitation. Exploitation requires a crafted archive containing a symlinked backup.yaml and access sufficient to submit or trigger its import. No exploit maturity or public proof-of-concept status is established by the bundle.
Researcher notes
The security boundary failure occurs when backup.yaml is represented by a symbolic link inside an imported archive. Processing the referenced metadata outside intended confinement can reach root command execution. The supplied data does not identify fixed versions, patch commits, exploitation telemetry, or proof-of-concept availability; consult the vendor advisory for those details.
Mitigation direction
- Check Canonical's advisory for fixed releases and upgrade instructions.
- Restrict image and backup import privileges to trusted administrators.
- Avoid importing archives from untrusted or unverified sources.
- Limit network access to LXD management interfaces until remediation is confirmed.
Validation and detection
- Inventory LXD installations and record their exact versions.
- Compare installed versions with Canonical's published affected and fixed release boundaries.
- Review who can upload, import, or restore LXD archives.
- Investigate recent archive imports and unexpected privileged host activity.
- Confirm remediation using approved defensive tests in an isolated environment.
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 lookupExecution behavior lookup
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.
Open ATT&CK lookupCVE-2026-63294 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-fv82-v4fj-mm4mCVE 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.