Skip to main content
VulnerabilityPublished

github.com/canonical/lxd · LXD has project restriction bypass for custom volume copy across projects

Affects github.com/canonical/lxdSource GCVE Database

0

CVSS 7.7 High : upgrade to 0.0.0-20260630083100-c5184be310b1 soon.

Data as of 6 Nov 2026, 20:27 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.0.0-20260630083100-c5184be310b1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

What to do

Upgrade github.com/canonical/lxd to 0.0.0-20260630083100-c5184be310b1.

Affected software

ProductAffectedFixed in
Gogithub.com/canonical/lxdAffected
  • <0.0.0-20260630083100-c5184be310b1
Fixed in
  • 0.0.0-20260630083100-c5184be310b1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in LXD version 0.0.0-20260630083100-c5184be310b1 that fixes this authorization bypass. Users should upgrade to this fixed version or later to remediate the vulnerability. Until patched, restrict access to trusted users only and monitor for unauthorized volume copying attempts. No vendor advisory states that no action is required or that it is already mitigated, so upgrading is recommended.

Description

LXD contains a vulnerability where missing authorization checks allow an attacker to copy a custom storage volume from a project they do not have access to into a project they control. This occurs because the source project field is attacker-controlled and not properly permission-checked before copying. Exploitation can lead to unauthorized access to secrets stored in custom volumes. A proof-of-concept script demonstrates how an attacker with valid credentials but restricted project access can copy volumes across projects on the same server.

References

Community reviews

Loading reviews…