CVE-2026-63295: Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated`
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.34% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Canonical LXD 4.0.12, 5.0.8, 5.21.6.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Canonical LXD 4.0.12, 5.0.8, 5.21.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 12, 2026
- Updated
- Oct 24, 2026
- EPSS
- 0.3% · 28th percentile
- CWE
- CWE-863
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · canonical
- 4.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| canonical | lxd | cpe:2.3:a:canonical:lxd |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical lxd4.0.0 and later · before 4.0.12
- canonical lxd5.0.0 and later · before 5.0.8
- canonical lxd5.1 and later · before 5.21.6
- canonical lxd6.0 and later · before 6.10
Versions reported by the vendor
Affected version ranges reported by the assigning authority (canonical). Independent of NVD's CPE analysis and usually ahead of it.
Canonical LXD
- 4.0.0 and later · before 4.0.12affected · semver
- 5.0.0 and later · before 5.0.8affected · semver
- 5.21.0 and later · before 5.21.6affected · semver
- 6.0 and later · before 6.10affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | lxd | from 0 | — |
| openSUSE:Leap 16.0 | lxd | before 5.21.6-bp160.1.1 | 5.21.6-bp160.1.1 |
Same product
canonical: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-112816Improper certificate validation in the HTTPS listener in LXD40Plan
- CVE-2026-87799Arbitrary file write on LXD host via symlink in migration stream39Monitor
- CVE-2026-85526Path traversal via Btrfs optimized-backup subvolumes[].path enables root file/dir manipulation in LXD39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-63293Aug 12, 2026 · Arbitrary File Read/Write: metadata.yaml symlink in image allows host filesystem access as root39Monitor
- ← EarlierCVE-2026-63294Aug 12, 2026 · Root RCE via image backup.yaml symlink39Monitor
- Later →CVE-2026-63296Aug 12, 2026 · Project restriction bypass via instance migration config override39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Canonical LXD | 4.0.12 | Vendor (CNA) |
| Canonical LXD | 5.0.8 | Vendor (CNA) |
| Canonical LXD | 5.21.6 | Vendor (CNA) |
| Canonical LXD | 6.10 | Vendor (CNA) |
| opensuse:lxd | 5.21.6-bp160.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-624200 days apartCross-project cluster migration bypasses project restrictions via cluster notification flag39Monitor
- CVE-2026-632960 days apartProject restriction bypass via instance migration config override39Monitor
- CVE-2026-9733547 days apartIncorrect authorization in LXD storage volume API allows reading volumes from other projects30Monitor
- CVE-2026-964047 days apartLXD Snapshot Import Privilege Escalation Vulnerability28Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0830 · Aug 13, 2026(Canonical LXD Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →