CVE-2026-34178

incus: In Canonical LXD before 6.8, the backup import path validates project restrictions against backup/index.yaml in the s...

CVE-2026-34178 is fixed in 3 products on 1 platform, first by DEBIAN-CVE-2026-34178, released April 9, 2026. It is not reported as exploited. Patch Radar priority: Urgent.

Urgent
CVSS
9.1
critical
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0043
37th percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
govulncheck-vulndb · opensuse-leap 16.0 0.0.20260827T195228-160000.1.1 OPENSUSE-SU-2026:21761-1 Sep 4, 2026
govulncheck-vulndb · sles 16.0 0.0.20260827T195228-160000.1.1 SUSE-SU-2026:23625-1 Sep 4, 2026
incus · Debian 13.5 (trixie) 6.0.4-2+deb13u6 DEBIAN-CVE-2026-34178 Apr 9, 2026
incus · Debian 14 6.0.6-3 DEBIAN-CVE-2026-34178 Apr 9, 2026
lxd · Debian 13.5 (trixie) 5.0.2+git20231211.1364ae4-9+deb13u5 DEBIAN-CVE-2026-34178 Apr 9, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.