CVE-2026-9640

HIGHPre-NVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 52% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A privilege escalation vulnerability exists in LXD from 6.0 before 6.9, 5.21.0 before 5.21.5, and 5.0.0 before 5.0.7 regarding the handling of project-restriction policies during snapshot restoration.. An authenticated project operator in a restricted multi-tenant environment can bypass policy restrictions by importing a maliciously crafted instance backup containing restricted configuration keys within a snapshot. When the snapshot is restored, these restricted keys are applied to the live instance without policy validation. Starting the modified instance grants the operator unauthorized host root access.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

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
Severity72% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 2, 2026

Advisory Details (4)

Auto-updated Jun 26, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github.
github Patch Available🟡 PoC Available

Backup snapshot import bypasses project restrictions · Advisory · canonical/lxd · GitHub

https://github.com/canonical/lxd/security/advisories/GHSA-ppq7-4492-5552
github_pr

Backports (stable-5.0)

Fix merged in canonical/lxd PR #18304 on 2026-05-20 — awaiting tagged release

https://github.com/canonical/lxd/pull/18304
github_pr

Backports (stable-5.21)

Fix merged in canonical/lxd PR #18303 on 2026-05-20 — awaiting tagged release

https://github.com/canonical/lxd/pull/18303
github_pr

Instance: Improve snapshot config validation during import

Fix merged in canonical/lxd PR #18301 on 2026-05-19 — awaiting tagged release

https://github.com/canonical/lxd/pull/18301

Affected Packages

(2 across 2 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
lxd5.0.2+git20231211.1364ae4-1 ... 5.0.2-6 (17 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
lxd5.0.2+git20231211.1364ae4-9 ... 5.0.2+git20231211.1364ae4-9+deb13u6 (7 versions)5.0.2+git20231211.1364ae4-9+deb13u7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9640?
CVE-2026-9640 is a high vulnerability published on June 26, 2026. A privilege escalation vulnerability exists in LXD from 6.0 before 6.9, 5.21.0 before 5.21.5, and 5.0.0 before 5.0.7 regarding the handling of project-restriction policies during snapshot restoration.. An authenticated project operator in a restricted multi-tenant environment can bypass policy…
When was CVE-2026-9640 disclosed?
CVE-2026-9640 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9640 actively exploited?
CVE-2026-9640 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.7% of all scored CVEs.
What is the CVSS score of CVE-2026-9640?
CVE-2026-9640 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-9640?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9640, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-9640?

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

Start Free Scan →Browse All CVEs