CVE-2026-34178 json
Importing a crafted backup leads to project restriction bypass
published 7mo ago modified 14d ago also GHSA-q96j-3fmm-7fv4 , GO-2026-5576 , EUVD-2026-20874
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
In Canonical LXD before 6.8, the backup import path validates project restrictions against backup/index.yaml in the supplied tar archive but creates the instance from backup/container/backup.yaml, a separate file in the same archive that is never checked against project restrictions. An authenticated remote attacker with instance-creation permission in a restricted project can craft a backup archive where backup.yaml carries restricted settings such as security.privileged=true or raw.lxc directives, bypassing all project restriction enforcement and allowing full host compromise.
Patch / fix
- Canonical lxd 5.0.7, 5.21.5, 6.8.0
- lxd Debian 13 5.0.2+git20231211.1364ae4-9+deb13u5
- incus Debian 13 6.0.4-2+deb13u6
- incus Debian 14 6.0.6-3
debian advisories DEBIAN-CVE-2026-34178
- govulncheck-vulndb SLES for SAP applications 16.0, SLES 16.0 0.0.20260827T195228-160000.1.1
suse advisories SUSE-SU-2026:23625-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260827T195228-160000.1.1
opensuse advisories openSUSE-SU-2026:21761-1
- github.com/canonical/lxd#17921 pull request
Is CVE-2026-34178 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 7mo ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/canonical/lxd/security/advisories/GHSA-q96j-3fmm-7fv4 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/canonical/lxd | >=0.0.0-20210305023314-538ac3df036e, <=0.0.0-20260226085519-736f34afb267 >=0.0.0-20210305023314-538ac3df036e |
no fix listed |
Affected products
- Canonical lxd
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/canonical/lxd/pull/17921
patch, issue-tracking, web
-
github.com
/canonical/lxd/security/advisories/GHSA-q96j-3fmm-7fv4
vdb-entry, vendor-advisory, exploit, web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-34178
advisory
-
github.com
/canonical/lxd
package
Sources
- CVE List CVE-2026-34178
- GitHub Advisory GHSA-q96j-3fmm-7fv4
- NVD CVE-2026-34178
- OSV GO-2026-5576
Fencer Intel 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.