Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 7.7, published 6 November 2026.
- Which products and versions are affected?
- github.com/canonical/lxd (Go) < 0.0.0-20260630083100-c5184be310b1, SEMVER:introduced=0,fixed=0.0.0-20260630083100-c5184be310b1.
- Is there a fix for This vulnerability?
- Yes. github.com/canonical/lxd (Go): upgrade to 0.0.0-20260630083100-c5184be310b1 or later. Until then: Restrict network access to the LXD API endpoint to trusted hosts and networks. Review project permissions and revoke access for certificates no longer needed.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-11-06"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a network appliance.
- Am I affected?
- Check whether you run github.com/canonical/lxd (Go) or Linux Containers 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.
How to fix
- github.com/canonical/lxd (Go): upgrade to 0.0.0-20260630083100-c5184be310b1 or later
go get github.com/canonical/lxd@v0.0.0-20260630083100-c5184be310b1
Restrict network access to the LXD API endpoint to trusted hosts and networks. Review project permissions and revoke access for certificates no longer needed.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-11-06"}]
Technical details
The storage volume creation handler in LXD fails to validate authorization on the source project before copying a custom volume. An attacker can specify an attacker-controlled source project name in the API request, and the system copies the volume without checking if the caller has view permissions on the source volume. The vulnerability requires network access to the LXD API and knowledge of a project name and volume name; successful exploitation grants the attacker access to the copied volume's contents.
Affected products
- Linux Containers LXD