Quick answers
- Is CVE-2026-97335 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97335 being exploited in the wild.
- How severe is CVE-2026-97335?
- High severity, with a CVSS score of 7.7, published 28 September 2026.
- Which products and versions are affected?
- Canonical LXD 5.0.0 through 5.0.9, 5.1.0 through 5.21.7, 6.0 through 6.9.
- Is there a fix for CVE-2026-97335?
- A patch was published on 2026-09-28: 5.0.10, 5.21.8, 6.9-bf243da, 6.10 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-97335 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-97335?
- Check whether you run Canonical LXD at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The POST /1.0/storage-pools/{pool}/volumes/custom endpoint performs insufficient authorization checks when a crafted request omits the source.type field. The access check for the source volume only runs when source.type is explicitly set to "copy", but requests without this field follow the same code path without validation. An authenticated client with can_create_storage_volumes permission in a project can exploit this by providing a source.project parameter pointing to another project, reading the target volume's contents, snapshots, and configuration.
Affected products
- Canonical LXD 5.0.0 through 5.0.9, 5.1.0 through 5.21.7, 6.0 through 6.9
Timeline
- 2026-09-25: disclosed
- 2026-09-28: patched: 5.0.10, 5.21.8, 6.9-bf243da, 6.10