Skip to content
Fencer Intel
critical 9.9

CVE-2026-63296 json

Project restriction bypass via instance migration config override

published 3mo ago modified 18d ago also EUVD-2026-57515 , GHSA-gcr9-5q6r-w625

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.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass target project restrictions during instance migration. When migrating an instance to a target project, LXD accepts configuration overrides without validating the new configuration against the target project's enforced restrictions. An attacker can exploit this flaw to move instances with disallowed high-privilege configurations into restricted projects, bypassing security controls.

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-63296 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
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
2mo ago

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/canonical/lxd/security/advisories/GHSA-gcr9-5q6r-w625 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.