Back to CVE records
High 7.2Published Jun 26, 2026

CVE-2026-9640A privilege escalation vulnerability exists in LXD from 6.0 before 6.9, 5.21.0 before 5.21.5, and 5.0.0 before 5.0.7 regarding the handling of project-restriction policies during snapshot restoration…

Updated under an hour ago ()

Does this affect you?

It affects canonical lxd. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

A privilege escalation vulnerability exists in LXD from 6.0 before 6.9, 5.21.0 before 5.21.5, and 5.0.0 before 5.0.7 regarding the handling of project-restriction policies during snapshot restoration.. An authenticated project operator in a restricted multi-tenant environment can bypass policy restrictions by importing a maliciously crafted instance backup containing restricted configuration keys within a snapshot. When the snapshot is restored, these restricted keys are applied to the live instance without policy validation. Starting the modified instance grants the operator unauthorized host root access.

CVSS
7.2 HIGH (v3.1, NVD)CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-863
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Not given
NVD analysis
Analyzed
Record last updated
Jul 2, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
canonical lxd
canonical:lxd
from 4.12 before 5.0.7; from 5.21.0 before 5.21.5; from 6.0 before 6.9
NVD

References

  • issue-tracking, patch
  • issue-tracking, patch
  • issue-tracking, patch
  • exploit

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.