CVE-2026-63295

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass project-level container isolation restrictions. When a project is configured with restrictions on container privileges (such as enforcing restricted.containers.privilege=isolated), LXD fails to enforce the requirement if an instance configuration omits the security.idmap.isolated key. An attacker can exploit this flaw by creating or updating an instance without explicitly setting security.idmap.isolated, bypassing the target project's security constraints.

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass project-level container isolation restrictions. When a project is configured with restrictions on container privileges (such as enforcing restricted.containers.privilege=isolated), LXD fails to enforce the requirement if an instance configuration omits the security.idmap.isolated key. An attacker can exploit this flaw by creating or updating an instance without explicitly setting security.idmap.isolated, bypassing the target project's security constraints.

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass project-level container isolation restrictions. When a project is configured with restrictions on container privileges (such as enforcing restricted.containers.privilege=isolated), LXD fails to enforce the requirement if an instance configuration omits the security.idmap.isolated key. An attacker can exploit this flaw by creating or updating an instance without explicitly setting security.idmap.isolated, bypassing the target project's security constraints.

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass project-level container isolation restrictions. When a project is configured with restrictions on container privileges (such as enforcing restricted.containers.privilege=isolated), LXD fails to enforce the requirement if an instance configuration omits the security.idmap.isolated key. An attacker can exploit this flaw by creating or updating an instance without explicitly setting security.idmap.isolated, bypassing the target project's security constraints.

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass project-level container isolation restrictions. When a project is configured with restrictions on container privileges (such as enforcing restricted.containers.privilege=isolated), LXD fails to enforce the requirement if an instance configuration omits the security.idmap.isolated key. An attacker can exploit this flaw by creating or updating an instance without explicitly setting security.idmap.isolated, bypassing the target project's security constraints.

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass project-level container isolation restrictions. When a project is configured with restrictions on container privileges (such as enforcing restricted.containers.privilege=isolated), LXD fails to enforce the requirement if an instance configuration omits the security.idmap.isolated key. An attacker can exploit this flaw by creating or updating an instance without explicitly setting security.idmap.isolated, bypassing the target project's security constraints.

This update for lxd fixes the following issues:

Changes in lxd:

• update to 5.21.6:

  • bsc#1274937, CVE-2026-63293, bsc#1274936, CVE-2026-62420, bsc#1274954, CVE-2026-63295, bsc#1274963, CVE-2026-63297, bsc#1274961, CVE-2026-63296, bsc#1275085, CVE-2026-63299, bsc#1275084, CVE-2026-63298, bsc#1275090, CVE-2026-66898
  • https://canonical.com/lxd/docs/latest/reference/release- notes/5.21/release-notes-5.21.6/
  • https://canonical.com/lxd/docs/latest/reference/release- notes/5.21/release-notes-5.21.5/
  • https://discourse.ubuntu.com/t/lxd-5-21-4-lts-has-been- released/66602
  • https://discourse.ubuntu.com/t/lxd-5-21-3-lts-has-been- released/53768
  • https://discourse.ubuntu.com/t/lxd-5-21-2-has-been- released/46443

• Migrate to single LXD/Incus OVMF handling (lxd-ovmf-setup):

  • Allow aarch64 arch_vm_support
  • Remove OVMF symlinks
  • Require the new lxd-ovmf-setup packages