CVE-2026-63293

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (46th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

Upgrade to LXD version 4.0.12 or later, 5.0.8 or later, or 5.12.6 or later, or 6.10 or later (from the CVE record's solution, Canonical Ltd.) — apply it.

A link following vulnerability in LXD allows an attacker to achieve arbitrary file read and write operations on the host system. When importing or unpacking an image archive, LXD fails to validate whether the metadata.yaml file is a symbolic link. An attacker can exploit this flaw by providing a crafted image archive with a symlinked metadata.yaml file pointing to target file paths on the host system.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
The EG Score, 9.9 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: Upgrade to LXD version 4.0.12 or later, 5.0.8 or later, or 5.12.6 or later, or 6.10 or later (from the CVE record's solution, Canonical Ltd.). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

Upgrade to LXD version 4.0.12 or later, 5.0.8 or later, or 5.12.6 or later, or 6.10 or later (from the CVE record's solution, Canonical Ltd.). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 12, 2026

Last Modified

September 3, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
Fix named in the CVE record's solution (Canonical Ltd.). Sources: github.
GitHub advisoryMentions a patch (unverified)

Arbitrary File Read/Write: metadata.yaml symlink in image allows host filesystem access as root · Advisory · canonical/lxd · GitHub

https://github.com/canonical/lxd/security/advisories/GHSA-j825-cg34-5fr5

Affected Packages

(2 across 2 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
lxd5.0.2+git20231211.1364ae4-1 ... 5.0.2-6 (17 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
lxd5.0.2+git20231211.1364ae4-9 ... 5.0.2+git20231211.1364ae4-9+deb13u7 (8 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 109 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 9 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 09:17 UTCEG score recompute
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-13 06:31 UTCEG score recompute
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-10-12 15:49 UTCEG score recompute
  6. 2026-10-11 19:33 UTCEG score recompute
  7. 2026-10-11 16:48 UTCEG score recompute
  8. 2026-10-11 14:10 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  14. 2026-10-06 18:16 UTCEG score recompute
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  16. 2026-10-05 18:58 UTCEG score recompute
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  18. 2026-10-05 02:33 UTCEG score recompute
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-10-03 19:56 UTCEG score recompute
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  22. 2026-10-02 21:58 UTCEG score recompute
  23. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  24. 2026-10-02 08:18 UTCEG score recompute
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 46th percentile
Show 75 more
  1. 2026-09-30 21:53 UTCEG score recompute
  2. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-09-29 04:28 UTCEG score recompute
  4. 2026-09-27 16:52 UTCEG score recompute
  5. 2026-09-27 09:52 UTCEG score recompute
  6. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  7. 2026-09-25 03:39 UTCEG score recompute
  8. 2026-09-23 20:53 UTCEG score recompute
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-09-22 21:05 UTCEG score recompute
  11. 2026-09-22 00:17 UTCEG score recompute
  12. 2026-09-20 20:24 UTCEG score recompute
  13. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-09-19 16:22 UTCEG score recompute
  15. 2026-09-18 23:00 UTCEG score recompute
  16. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-09-17 22:28 UTCEG score recompute
  18. 2026-09-17 00:17 UTCEG score recompute
  19. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-09-16 06:10 UTCEG score recompute
  21. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-09-15 06:23 UTCEG score recompute
  23. 2026-09-13 19:32 UTCEG score recompute
  24. 2026-09-12 18:35 UTCEG score recompute
  25. 2026-09-11 17:51 UTCEG score recompute
  26. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  27. 2026-09-11 13:46 UTCEG score recompute
  28. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  29. 2026-09-10 09:58 UTCEG score recompute
  30. 2026-09-09 05:11 UTCEG score recompute
  31. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  32. 2026-09-07 16:41 UTCEG score recompute
  33. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  34. 2026-09-06 14:31 UTCEG score recompute
  35. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  36. 2026-09-05 17:46 UTCEG score recompute
  37. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  38. 2026-09-04 16:05 UTCEG score recompute
  39. 2026-09-04 07:53 UTCEG score recompute
  40. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  41. 2026-09-02 23:26 UTCEG score recompute
  42. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  43. 2026-09-01 16:29 UTCEG score recompute
  44. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  45. 2026-09-01 06:22 UTCEG score recompute
  46. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  47. 2026-08-30 21:14 UTCEG score recompute
  48. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  49. 2026-08-30 04:45 UTCEG score recompute
  50. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  51. 2026-08-29 08:32 UTCEG score recompute
  52. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  53. 2026-08-27 16:29 UTCEG score recompute
  54. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  55. 2026-08-26 14:48 UTCEG score recompute
  56. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  57. 2026-08-25 13:59 UTCEG score recompute
  58. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  59. 2026-08-24 17:24 UTCEG score recompute
  60. 2026-08-24 13:14 UTCEG score recompute
  61. 2026-08-23 00:24 UTCEG score recompute
  62. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  63. 2026-08-21 23:51 UTCEG score recompute
  64. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  65. 2026-08-20 23:18 UTCEG score recompute
  66. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  67. 2026-08-19 18:34 UTCEG score recompute
  68. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  69. 2026-08-18 17:16 UTCEG score recompute
  70. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  71. 2026-08-17 16:00 UTCEG score recompute
  72. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  73. 2026-08-16 15:29 UTCEG score recompute
  74. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  75. 2026-08-16 03:14 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-63293?
CVE-2026-63293 is a critical-severity vulnerability; its CVE record was published on August 12, 2026. A link following vulnerability in LXD allows an attacker to achieve arbitrary file read and write operations on the host system. When importing or unpacking an image archive, LXD fails to validate whether the metadata.yaml file is a symbolic link. An attacker can exploit this flaw by providing a…
When was the CVE record for CVE-2026-63293 published?
The CVE record for CVE-2026-63293 was published on August 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 3, 2026; the record at its source may have been updated since.
Is CVE-2026-63293 actively exploited?
CVE-2026-63293 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63293?
CVE-2026-63293 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63293?
The CVE record's solution for CVE-2026-63293, written by its CNA Canonical Ltd., names the fix: "Upgrade to LXD version 4.0.12 or later, 5.0.8 or later, or 5.12.6 or later, or 6.10 or later."

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63293

Explore →

Is Your Infrastructure Affected by CVE-2026-63293?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs