Skip to content
Cloud

CVE-2026-63296

9.9
Critical
EPSS 0.30%Patch availableAug 13, 2026

Auth bypass in LXD allows migrating high-privilege instances into restricted projects.

common questions

Is CVE-2026-63296 being exploited?

Not confirmed. CVE-2026-63296 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-63296?

CVE-2026-63296 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-63296?

Yes. A fix has been recorded for CVE-2026-63296. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-63296 affect?

CVE-2026-63296 affects LXD (container manager), LXD project namespaces, Linux container instances. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-63296?

Apply vendor patch when released; block/audit cross-project migrations and restrict migration privileges.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
LXD (container manager)LXD project namespacesLinux container instances
impact

Authenticated attacker can bypass project restrictions during instance migration to inject disallowed high-privilege configs, enabling privilege escalation and unauthorized access.

action required

Immediate action required

affected versions
Canonical LXD
  • affected>= 5.0.0 and < 5.0.8
  • affected>= 5.21.0 and < 5.21.6
  • affected>= 6.0 and < 6.10

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free