This weekExploitable · Confirmed
github.com/canonical/lxd: LXD has CreateCustomVolumeFromBackup nil-pointer dereference on volumes[0].snapshots[*].expires_at
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): every version, before 0.0.0-20260622081844-85f897013ccd
The fix
github.com/canonical/lxd (Go) fixed in 0.0.0-20260622081844-85f897013ccd
gogo get github.com/canonical/lxd@v0.0.0-20260622081844-85f897013ccdCheck what is installedgo list -m github.com/canonical/lxdPaste into Cursor, Lovable or Claude CodeUpgrade the Go dependency github.com/canonical/lxd to 0.0.0-20260622081844-85f897013ccd or the nearest later release, to fix CVE-2026-9639. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
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))