CVE-2026-63295

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (26th 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
4.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.3%CVSS: 4.3Exploit: 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.

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass project-level container isolation restrictions. When a project is configured with restrictions on container privileges (such as enforcing restricted.containers.privilege=isolated), LXD fails to enforce the requirement if an instance configuration omits the security.idmap.isolated key. An attacker can exploit this flaw by creating or updating an instance without explicitly setting security.idmap.isolated, bypassing the target project's security constraints.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
35
EG Risk 35/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)
Severity43% × 45%
The EG Score, 4.3 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 11, 2026

Advisory Details (1)

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

Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated` · Advisory · canonical/lxd · GitHub

https://github.com/canonical/lxd/security/advisories/GHSA-7vp9-3vmp-c5jm

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 11× in last 7d / 40× 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.

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

Frequently asked(5)

What is CVE-2026-63295?
CVE-2026-63295 is a medium-severity vulnerability; its CVE record was published on August 12, 2026. An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass project-level container isolation restrictions. When a project is configured with restrictions on container privileges (such as enforcing restricted.containers.privilege=isolated), LXD fails to enforce the…
When was the CVE record for CVE-2026-63295 published?
The CVE record for CVE-2026-63295 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 11, 2026; the record at its source may have been updated since.
Is CVE-2026-63295 actively exploited?
CVE-2026-63295 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63295?
CVE-2026-63295 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63295?
The CVE record's solution for CVE-2026-63295, 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-63295

Explore →

Is Your Infrastructure Affected by CVE-2026-63295?

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