p PatchFirst

CVE-2026-34178

CVE-2026-34178 · Importing a crafted backup leads to project restriction bypass

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 9.1 · Critical · EPSS 0.4% · Fix available

Published
Updated

Stack: system

Affected products and versions

  • lxd

    Versions
    • ≥ 4.12.0, < 5.0.7: Affected (semver)
    • ≥ 5.1.0, < 5.21.5: Affected (semver)
    • ≥ 6.0.0, < 6.8.0: Affected (semver)

    Update to 5.0.7; Update to 5.21.5; Update to 6.8.0

  • incus Debian:13

    Versions
    • 6.0.4-2
    • 6.0.4-2+deb13u1
    • 6.0.4-2+deb13u1~bpo12+1
    • 6.0.4-2+deb13u2
    • 6.0.4-2+deb13u2~bpo12+1
    • 6.0.4-2+deb13u3
    • 6.0.4-2+deb13u3~bpo12+1
    • 6.0.4-2+deb13u4
    • 6.0.4-2+deb13u4~bpo12+1
    • 6.0.4-2+deb13u5
    • 6.0.4-2+deb13u5~bpo12+1
    • 6.0.4-2+deb13u6~bpo12+1
    Affected ranges
    • ECOSYSTEM: < 6.0.4-2+deb13u6

    Update to 6.0.4-2+deb13u6

  • incus Debian:14

    Versions
    • 6.0.4-2
    • 6.0.4-3
    • 6.0.5-1
    • 6.0.5-2
    • 6.0.5-3
    • 6.0.5-4
    • 6.0.5-5
    • 6.0.5-6
    • 6.0.5-7
    • 6.0.5-8
    • 6.0.6-1
    • 6.0.6-2
    Affected ranges
    • ECOSYSTEM: < 6.0.6-3

    Update to 6.0.6-3

  • lxd Debian:12

    Versions
    • 5.0.2+git20231211.1364ae4-1
    • 5.0.2+git20231211.1364ae4-2
    • 5.0.2+git20231211.1364ae4-3
    • 5.0.2+git20231211.1364ae4-4
    • 5.0.2+git20231211.1364ae4-5
    • 5.0.2+git20231211.1364ae4-6
    • 5.0.2+git20231211.1364ae4-7
    • 5.0.2+git20231211.1364ae4-8
    • 5.0.2+git20231211.1364ae4-9
    • 5.0.2-5
    • 5.0.2-5+deb12u1
    • 5.0.2-5+deb12u2
    • 5.0.2-5+deb12u3
    • 5.0.2-5+deb12u4
    • 5.0.2-5+deb12u5
    • 5.0.2-5+deb12u6
    • 5.0.2-6
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • lxd Debian:13

    Versions
    • 5.0.2+git20231211.1364ae4-9
    • 5.0.2+git20231211.1364ae4-9+deb13u1
    • 5.0.2+git20231211.1364ae4-9+deb13u2
    • 5.0.2+git20231211.1364ae4-9+deb13u3
    • 5.0.2+git20231211.1364ae4-9+deb13u4
    Affected ranges
    • ECOSYSTEM: < 5.0.2+git20231211.1364ae4-9+deb13u5

    Update to 5.0.2+git20231211.1364ae4-9+deb13u5

  • incus Ubuntu:Pro:24.04:LTS

    Versions
    • 0.4-1ubuntu1
    • 0.5.1-1
    • 0.5.1-3
    • 0.6-1
    • 6.0.0-1
    • 6.0.0-1ubuntu0.1
    • 6.0.0-1ubuntu0.2
    • 6.0.0-1ubuntu0.2+esm1
    • 6.0.0-1ubuntu0.3
    • 6.0.0-1ubuntu0.3+esm1
    • 6.0.0-1ubuntu0.3+esm2
    • 6.0.0-1ubuntu0.3+esm3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • incus Ubuntu:25.10

    Versions
    • 6.0.3-4
    • 6.0.4-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • incus Ubuntu:26.10

    Versions
    • 6.0.5-8
    • 7.0.1-5
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • incus Ubuntu:Pro:26.04:LTS

    Versions
    • 6.0.4-2
    • 6.0.5-8
    • 6.0.5-8ubuntu0.26.04.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →