CVE-2026-9640 | LXD Snapshot Import Privilege Escalation Vulnerability

Exp

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.

Published: 2026-06-26 Last update: 2026-07-02 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-9640 is rated Exploit Available (52.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.33%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-9640

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-9640

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-27 — 0.33% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-9640

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.2 5.9 [email protected]

Weakness enumeration for CVE-2026-9640

OS Trackers for CVE-2026-9640

vendor priority summary link
debian end-of-life CVE-2026-9640 end-of-life priority: Debian including 1 source packages (lxd), 2 status rows across 2 suites (bookworm, trixie): open 1, resolved 1. https://security-tracker.debian.org/tracker/CVE-2026-9640
ubuntu medium CVE-2026-9640 medium priority: Ubuntu including 1 source packages (lxd), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, resolute, upstream, xenial): DNE 4, not-affected 3, needs-triage 1. https://ubuntu.com/security/CVE-2026-9640

Affected software / configurations for CVE-2026-9640

Vendor Product Version Raw CPE
canonical lxd >= 4.12, < 5.0.7 cpe:2.3:a:canonical:lxd:*:*:*:*:*:*:*:*
canonical lxd >= 5.21.0, < 5.21.5 cpe:2.3:a:canonical:lxd:*:*:*:*:*:*:*:*
canonical lxd >= 6.0, < 6.9 cpe:2.3:a:canonical:lxd:*:*:*:*:*:*:*:*

References for CVE-2026-9640

cvelogic Threat Intelligence