CVE-2026-62420

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass target project security restrictions during cross-project instance migrations. When moving an instance cross-project to a different cluster member via POST /1.0/instances/{name} with migration: true, project: <target>, and target: <member>, the destination node skips all project restriction checks because the request arrives as an internal cluster notification. An attacker can exploit this to introduce disallowed instance configurations into a restricted project.

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass target project security restrictions during cross-project instance migrations. When moving an instance cross-project to a different cluster member via POST /1.0/instances/{name} with migration: true, project: <target>, and target: <member>, the destination node skips all project restriction checks because the request arrives as an internal cluster notification. An attacker can exploit this to introduce disallowed instance configurations into a restricted project.

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass target project security restrictions during cross-project instance migrations. When moving an instance cross-project to a different cluster member via POST /1.0/instances/{name} with migration: true, project: <target>, and target: <member>, the destination node skips all project restriction checks because the request arrives as an internal cluster notification. An attacker can exploit this to introduce disallowed instance configurations into a restricted project.

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass target project security restrictions during cross-project instance migrations. When moving an instance cross-project to a different cluster member via POST /1.0/instances/{name} with migration: true, project: <target>, and target: <member>, the destination node skips all project restriction checks because the request arrives as an internal cluster notification. An attacker can exploit this to introduce disallowed instance configurations into a restricted project.

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass target project security restrictions during cross-project instance migrations. When moving an instance cross-project to a different cluster member via POST /1.0/instances/{name} with migration: true, project: <target>, and target: <member>, the destination node skips all project restriction checks because the request arrives as an internal cluster notification. An attacker can exploit this to introduce disallowed instance configurations into a restricted project.

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass target project security restrictions during cross-project instance migrations. When moving an instance cross-project to a different cluster member via POST /1.0/instances/{name} with migration: true, project: <target>, and target: <member>, the destination node skips all project restriction checks because the request arrives as an internal cluster notification. An attacker can exploit this to introduce disallowed instance configurations into a restricted project.

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