Skip to content
Fencer Intel
critical 9.9

CVE-2026-62420 json

Cross-project cluster migration bypasses project restrictions via cluster notification flag

published 3mo ago modified 18d ago also EUVD-2026-57415 , GHSA-v9wr-9r7q-fh4g

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository canonical/lxd. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

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.

Patch / fix

  • Canonical LXD 5.0.8, 5.21.6, 6.10
  • lxd openSUSE Leap 16.0 5.21.6-bp160.1.1

opensuse advisories openSUSE-SU-2026:21788-1

Is CVE-2026-62420 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2mo ago

Exploit prediction

0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/canonical/lxd/security/advisories/GHSA-v9wr-9r7q-fh4g referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected products

  • Canonical LXD

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of canonical/lxd published their own advisory on GitHub. Reviewed sources take precedence over it.