CVE-2026-62420: Canonical LXD · Incorrect Authorization
Affects Canonical LXDSource CVE Database V5
Not known to be exploited · CVSS 9.9 Critical · fixed in 6.10 : patch Canonical LXD as a priority.
Data as of 9 Nov 2026, 23:24 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.10, 5.21.6, 5.0.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade Canonical LXD to 6.10, 5.21.6 or 5.0.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CanonicalLXD | Affected
| Fixed in
|
| CanonicalLXD | Affected
| Fixed in
|
| CanonicalLXD | Affected
| Fixed in
|
GitHubLXDpkg:github/LXDOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, administrators should consider restricting access to authenticated users and carefully monitor cross-project migration activities. No vendor advisory or patch links are currently available.
Description
An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass target project security restrictions during cross-project instance migrations. When moving an instance cross-project to a different cluster member via POST /1.0/instances/{name} with migration: true, project: <target>, and target: <member>, the destination node skips all project restriction checks because the request arrives as an internal cluster notification. An attacker can exploit this to introduce disallowed instance configurations into a restricted project.