A certificate chain is a list. The server is supposed to check the list properly. In LXD and MicroCloud it checked each item against its trust store separately, and that single shortcut earned a CVSS score of 10.0.
The flaw in plain terms
LXD, Canonical's system container and VM manager, and MicroCloud, its small-cluster product, authenticate remote clients with mutual TLS. As The Hacker News explains, the handshake only proves the client holds the private key for the first (leaf) certificate it presents. Anything else the client attaches is just along for the ride. The bug, CVE-2026-112816, is that the server tested every certificate in the presented chain against the trust store. So an attacker can send their own certificate, then append the public certificate of a client the server already trusts. The server sees a trusted certificate and lets them in as that client. Public certificates are not secrets, which is the whole problem.
If the impersonated identity is privileged, Canonical says the result is root on the host.
Who is actually exposed
This is not every LXD box on the internet. A standalone LXD server listens only on a local socket unless someone has switched on the network API with core.https_address. The preconditions are network reach to the HTTPS API and a trusted client's public certificate. MicroCloud is worse placed, since an attacker who captures a member's certificate as it joins the cluster can then act as that member.
The Incus project, the community fork of LXD, found the problem (GHSA-xg75-xf37-cph9) and fixed it in 7.6.0. Canonical confirmed LXD was affected too. There is no sign of exploitation, it is not on CISA's Known Exploited Vulnerabilities list, and no public exploit has been published at the time of writing. That window is the time you have.
Fixed versions
- LXD snaps: 6.10.1 (6/stable), 5.21.9, 5.0.11, 4.0.15
- MicroCloud snaps: 3.4.1 (3/stable), 2.1.5
- Incus: 7.6.0, which also closes 17 other security issues
Ubuntu archive packages of LXD are listed as not affected, so the fix is in the snaps. Canonical noted that some point releases were still moving from candidate to stable when it published, so refresh and then confirm the version rather than assuming.
Checklist
- Find out where the API is enabled. Search configs for
core.https_addressand any cluster setups. Local-socket-only hosts are low priority. - Refresh and verify:
sudo snap refresh lxd,sudo snap refresh microcloud, then check the installed version. - Restrict the listener to a management network or firewall allow-list until patched. For Incus that is the only mitigation offered.
- Review trusted clients and their privileges. If a certificate that can reach root on a host is sitting in a repo or on a shared drive, treat it as exposed context.
- Check logs for unexpected API logins from addresses outside your admin ranges.
The wider lesson is old and keeps returning: verifying that a certificate is trusted is different from verifying that the sender owns it. If you run self-built mutual TLS anywhere, test that exact case. We are happy to help review: sales@halfteck.com.
Sources: The Hacker News, 1 November 2026.