CVE-2026-34178 | Canonical LXD up to 5.0.6/5.21.4/6.7.x Backup Import backup/index.yaml input validation

VDB-356510 · CVE-2026-34178 · GCVE-0-2026-34178 CANONICAL LXD UP TO 5.0.6/5.21.4/6.7.X BACKUP IMPORT BACKUP/INDEX.YAML INPUT VALIDATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 8.0 $0-$5k 1.26+ Summaryinfo A vulnerability classified as critical was found in Canonical LXD up to 5.0.6/5.21.4/6.7.x. Affected by this vulnerability is an unknown functionality of the file backup/index.yaml of the component Backup Import. Such manipulation leads to input validation. This vulnerability is referenced as CVE-2026-34178. It is possible to launch the attack remotely. No exploit is available. Upgrading the affected component is advised. Detailsinfo A vulnerability, which was classified as critical, has been found in Canonical LXD up to 5.0.6/5.21.4/6.7.x. Affected by this issue is an unknown function of the file backup/index.yaml of the component Backup Import. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is confidentiality, integrity, and availability. CVE summarizes: 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. The weakness was published by Miha Purg. The advisory is available at github.com. This vulnerability is handled as CVE-2026-34178 since 03/26/2026. The exploitation is known to be easy. The attack may be launched remotely. The exploitation requires an enhanced level of successful authentication. Technical details are known, but there is no available exploit. Upgrading to version 5.0.7, 5.21.5 or 6.8.0 eliminates this vulnerability. Productinfo Vendor Canonical Name LXD Version 5.0.0 5.0.1 5.0.2 5.0.3 5.0.4 5.0.5 5.0.6 5.21.0 5.21.1 5.21.2 5.21.3 5.21.4 6.0 6.1 6.2 6.3 6.4 6.5 6.6 6.7 License open-source Website Product: https://github.com/canonical/lxd/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 8.1 VulDB Meta Temp Score: 8.0 VulDB Base Score: 7.2 VulDB Temp Score: 6.9 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 9.1 CNA Vector (canonical): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Input validation CWE: CWE-20 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: LXD 5.0.7/5.21.5/6.8.0 Timelineinfo 03/26/2026 CVE reserved 04/09/2026 +13 days Advisory disclosed 04/09/2026 +0 days VulDB entry created 04/09/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Researcher: Miha Purg Status: Confirmed CVE: CVE-2026-34178 (🔒) GCVE (CVE): GCVE-0-2026-34178 GCVE (VulDB): GCVE-100-356510 Entryinfo Created: 04/09/2026 11:49 Changes: 04/09/2026 11:49 (65) Complete: 🔍 Cache ID: 99:7AF:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸