This weekExploitable · Confirmed
github.com/canonical/lxd: LXD: Importing a crafted backup leads to project restriction bypass
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
github.com/canonical/lxd (Go)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- github.com/canonical/lxd (Go): from 0.0.0-20210305023314-538ac3df036e, up to and including 0.0.0-20260226085519-736f34afb267
- github.com/canonical/lxd (Go): from 0.0.0-20210305023314-538ac3df036e, with no fixed release listed
The fix
No fix yet: isolate it or follow the vendor's mitigation.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
CISA's assessment in the CVE record says a proof of concept is public.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))