Technical impact
The vulnerability arises because LXD's HTTPS listener accepts certificate chains without proper validation. An unauthenticated attacker can forge a chain that appears to be trusted, causing the system to believe the client is a legitimate member of the cluster. This bypass gives the attacker full administrative rights over the cluster and any virtual machines it manages, effectively enabling arbitrary code execution on hosts that run affected LXD versions.
Affected Systems
The flaw affects Canonical LXD releases 4.0.14, 5.0.10, 5.21.8, and 6.9 prior to 4.0.15, 5.0.11, 5.21.9 and 6.10.1. These versions are distributed as part of Ubuntu LTS packages and are also compatible with bare‑metal deployments. Customers using any of these LXD variants are at risk until they apply the vendor‑issued fix.
Risk and Exploitability
The CVSS score of 10 marks this as a critical vulnerability; no EPSS score is available and the issue is not listed in the CISA KEV catalog. The attack vector is remote over the HTTPS listener, meaning the attacker only needs network access to the LXD API endpoint and can craft a malicious certificate chain. Because authentication is bypassed entirely, the vulnerability is exploitable without any local privileges, and once achieved, the attacker can control the entire cluster. The risk remains high until the software is hardened or upgraded.