CVE-2026-63295 json
Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated`
published 2026-08-12 2 mo ago modified 2026-10-24 15 d ago also EUVD-2026-57516
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass project-level container isolation restrictions. When a project is configured with restrictions on container privileges (such as enforcing restricted.containers.privilege=isolated), LXD fails to enforce the requirement if an instance configuration omits the security.idmap.isolated key. An attacker can exploit this flaw by creating or updating an instance without explicitly setting security.idmap.isolated, bypassing the target project's security constraints.
Patch / fix
- Canonical LXD 4.0.12, 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
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/canonical/lxd/security/advisories/GHSA-7vp9-3vmp-c5jm referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
Affected products
- Canonical LXD
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/canonical/lxd/security/advisories/GHSA-7vp9-3vmp-c5jm
vdb-entry, vendor-advisory, exploit
Sources
- CVE List CVE-2026-63295
- NVD CVE-2026-63295
Fencer Vulns 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.