#Lxd

LXD host escapes via malicious images, backup compression, and project-restriction bypasses (GHSA-jpf8 / GHSA-9j25 / GHSA-vghh / GHSA-pjff / GHSA-fmc8 / GHSA-47w9 / GHSA-7mr3 / GHSA-qx75)

On Nov 6 2026 Canonical published a wave of critical LXD advisories (CVSS 9.9) for host escapes. Already tracked: GHSA-jpf8-86f3-wp38 / CVE-2026-48752 (templates/ symlink AFRW) and GHSA-9j25-mm2h-2f76 / CVE-2026-48750 (exec-output symlink AFW). Same-day additions: GHSA-vghh-5rfx-xhq8 / CVE-2026-48749 (rootfs/ symlink AFRW in a crafted image); GHSA-pjff-c2wc-f6jm / CVE-2026-48769 (arbitrary file write via trusted Incus-Image-Hash path traversal on source.type=url downloads); GHSA-fmc8-p6q7-75cc / CVE-2026-48755 (backup compression_algorithm argument injection leading to AFW/ACE). All were reported from the Incus fork. Fixes are in the github.com/canonical/lxd Go module; upgrade to fixed builds that include the advisory commits / firstPatched versions. Also folded GHSA-47w9-6r3f-938g / CVE-2026-48751: instance snapshots ignore `restricted.containers.lowlevel=block`, allowing abuse of raw.lxc / raw.qemu hooks for host ACE after moving a crafted snapshot into a restricted project; LXD >= 4.12 affected; patched in 6.9 / 5.21.5 / 5.0.7 (reported from Incus GHSA-48q5-w887-33wv; originally published Jun 26 2026, resurfaced in the Nov 6 critical GHSA wave). Further folded high-severity project-restriction bypasses GHSA-7mr3-28h5-m5vx (custom volume copy across projects) and GHSA-qx75-2p3r-pwm5 (instance copy across projects): authenticated caller knowing source project/volume or instance names can copy secrets they should not view; LXD >= 4.12; patched in 5.0.7 / 5.21.5 / 6.8 (note 6.8, not only 6.9); GHSA firstPatched Go module 0.0.0-20260630083100-c5184be310b1; reported from Incus GHSA-64f3-v33m-w89f and GHSA-c9f5-j9c3-mhrg; no CVE IDs assigned on the GitHub Advisory records as of this fold.

Canonical LXD (Incus fork also affected)·Since Nov 6, 2026·updated Nov 7, 2026, 12:15 UTC