Incorrect authorization in the custom storage volume creation endpoint in Canonical LXD versions 5.0.0 and later (fixed in 5.0.10, 5.21.8 and 6.10) on Linux allows an authenticated client with permission to create custom volumes in a project to copy, and so read, any custom storage volume from any other project on the server, including its snapshots and configuration. The client does this with a crafted request that sets a source volume and source.project but omits source.type.
CVE-2026-97335
HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (9th 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
7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.7Exploit: None knownExposed services: Not assessed
Upgrade to LXD versions 5.0.10, 5.21.8, 6.10 or later (from the CVE record's solution, Canonical Ltd.) — apply it.
- CVSS v3
- 7.7
- EG Score
- 7.7HIGHmedium confidence
- EG Risk
- 35EG 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)Severity77% × 45%The EG Score, 7.7 of 10.Exploitation0.2% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (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 versions 5.0.10, 5.21.8, 6.10 or later (from the CVE record's solution, Canonical Ltd.). Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 9th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
Upgrade to LXD versions 5.0.10, 5.21.8, 6.10 or later (from the CVE record's solution, Canonical Ltd.). Apply it within your standard update timelines.
Exploitation none (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
September 28, 2026
Last Modified
September 28, 2026
Advisory Details (1)
Auto-updated Sep 28, 2026Fix named in the CVE record's solution (Canonical Ltd.). Sources: github.
GitHub advisoryMentions a patch (unverified)
Project restriction bypass for custom volume copy with omitted source type · Advisory · canonical/lxd · GitHub
https://github.com/canonical/lxd/security/advisories/GHSA-p456-92fx-44xhAffected Packages
(2 across 2 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| lxd | 5.0.2+git20231211.1364ae4-1 ... 5.0.2-6 (17 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| lxd | 5.0.2+git20231211.1364ae4-9 ... 5.0.2+git20231211.1364ae4-9+deb13u7 (8 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 36× 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.
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-12 14:40 UTCEG score recompute
- 2026-10-11 19:11 UTCEG score recompute
- 2026-10-11 16:26 UTCEG score recompute
- 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-11 13:38 UTCEG score recompute
- 2026-10-11 12:34 UTCEG score recompute
- 2026-10-11 01:03 UTCEG score recompute
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-10 02:28 UTCEG score recompute
- 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-09 03:20 UTCEG score recompute
- 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-08 02:33 UTCEG score recompute
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-06 16:48 UTCEG score recompute
- 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-05 18:18 UTCEG score recompute
- 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-05 07:04 UTCEG score recompute
- 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-03 21:20 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-02 22:51 UTCEG score recompute
- 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 11 moreShow fewer
- 2026-10-02 00:18 UTCEG score recompute
- 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-01 01:50 UTCEG score recompute
- 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-09-29 16:06 UTCEG score recompute
- 2026-09-29 04:51 UTCEG score recompute
- 2026-09-28 17:37 UTCEG score recompute
- 2026-09-28 16:42 UTCEG score recompute
- 2026-09-28 14:24 UTCEG score recompute
- 2026-09-28 13:27 UTCEG score recomputeFirst assessed: 7.7 HIGH
- 2026-09-28 13:27 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownDebian:12:lxd
Frequently asked(5)
What is CVE-2026-97335?
CVE-2026-97335 is a high-severity vulnerability; its CVE record was published on September 28, 2026. Incorrect authorization in the custom storage volume creation endpoint in Canonical LXD versions 5.0.0 and later (fixed in 5.0.10, 5.21.8 and 6.10) on Linux allows an authenticated client with permission to create custom volumes in a project to copy, and so read, any custom storage volume from any…
When was CVE-2026-97335 made public?
CVE-2026-97335 was made public on September 25, 2026: that is the date its CVE record's CNA, Canonical Ltd., gives for when the vulnerability was made public. The CVE record itself was published on September 28, 2026. EchelonGraph's copy of the record carries a last-modified date of September 28, 2026; the record at its source may have been updated since.
Is CVE-2026-97335 actively exploited?
CVE-2026-97335 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97335?
CVE-2026-97335 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97335?
The CVE record's solution for CVE-2026-97335, written by its CNA Canonical Ltd., names the fix: "Upgrade to LXD versions 5.0.10, 5.21.8, 6.10 or later."
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-97335
Is Your Infrastructure Affected by CVE-2026-97335?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.