Skip to main content
HIGH Vulnerabilities #Root Access

CVE-2026-112816: LXD & MicroCloud Impersonation to Root Access

4 min read Runtime Rebel Intel
Primary source: thehackernews.com

This article was written by a language model from the source above and was not reviewed by a human before publication. Verify anything operational against the original. Editorial policy

Key points
  • Attackers can impersonate trusted LXD/MicroCloud clients, potentially gaining root access to host machines.
  • Canonical LXD versions 4.0.14, 5.0.10, 5.21.8, 6.9, and MicroCloud are vulnerable to this flaw.
  • Immediately update LXD and MicroCloud snap packages to the fixed versions.

Advertisement

Critical LXD and MicroCloud Impersonation Flaw (CVE-2026-112816) Enables Root Access

A significant vulnerability, tracked as CVE-2026-112816, has been identified in Canonical’s LXD and MicroCloud, allowing unauthenticated attackers to impersonate trusted clients. This flaw, which carries a maximum CVSS score of 10.0, could enable an attacker to gain root access to the host machine if the impersonated client possesses privileged access. While there is no public evidence of in-the-wild exploitation, the potential for severe impact necessitates immediate attention from administrators using these container and cluster management tools. The vulnerability was initially reported by the Incus project, a community fork of LXD, and subsequently confirmed by Canonical to affect LXD.

According to The Hacker News, the core issue lies in how LXD and MicroCloud validate client certificates during mutual TLS (mTLS) authentication to their HTTPS API. In a typical mTLS setup, clients present a certificate to prove their identity, and the server verifies this against its trust store, which contains a list of accepted identities.

CVE-2026-112816 Exploitation Details

The flaw in CVE-2026-112816 exploitation details centers on the server’s certificate chain validation process. While the TLS connection itself only cryptographically proves that the client possesses the private key for the leaf certificate (the first certificate in the chain presented by the client), the vulnerable LXD/MicroCloud server mistakenly compared every certificate in the client-provided chain against its internal trust store.

This critical oversight permits an attacker to construct a malicious certificate chain. They can take a trusted client’s public certificate – which is generally not considered a secret – and attach it as a secondary certificate behind their own attacker-controlled leaf certificate. When this manipulated chain is presented, the server’s flawed logic would identify the trusted client’s public certificate within the chain and erroneously grant the attacker access as if they were that trusted client. If the impersonated client account is configured with high privileges, such as administrative access, the attacker could escalate to root access on the host machine.

Two primary conditions are required for an attacker to leverage this vulnerability:

  • Network access to the HTTPS API: For standalone LXD servers, this API is not exposed by default, listening only on a local socket. Administrators must explicitly enable network exposure using the core.https_address setting.
  • The public certificate of an already trusted client: This certificate is not a secret and can potentially be intercepted or obtained through various means.

In the context of MicroCloud, which clusters multiple LXD machines, a specific weak point exists: an attacker capable of capturing a member’s public certificate as it joins the cluster could then use that certificate to log in as that member, leveraging this impersonation flaw.

Affected Versions and Status

The following LXD versions are specifically listed as affected before their respective fixed releases:

  • LXD 4.0.14
  • LXD 5.0.10
  • LXD 5.21.8
  • LXD 6.9

Canonical has released fixed versions, primarily delivered through snap packages. Ubuntu’s archive packages of LXD are noted as either not affected or not shipped with the vulnerable components. The Incus project addressed the same flaw in version 7.6.0, alongside 17 other security issues.

It is important to note that as of October 30, the U.S. CISA has assessed that CVE-2026-112816 is not known to have been exploited in the wild. It is not currently listed on CISA’s Known Exploited Vulnerabilities catalog, and no public working exploit has been published. However, the severity of the flaw dictates proactive patching.

Mitigating LXD Root Access Vulnerability

The primary and most critical action for administrators is to immediately update LXD snap versions and MicroCloud to the patched releases.

  • For snap installations: Run sudo snap refresh lxd and sudo snap refresh microcloud.
  • Verification: Canonical advises administrators to check the actual version installed after refreshing, as the fixed point releases for LXD were still rolling out from the candidate channel to stable at the time of their advisory. Do not assume the fix has arrived without confirmation.
  • Incus Users: Update to Incus 7.6.0 or later.

Until patching is complete, a crucial temporary mitigation for mitigating LXD root access vulnerability is to restrict network access to the HTTPS API listener. Since exploitation requires network connectivity to this API, limiting who can reach it significantly reduces the attack surface. Canonical’s advisory offers no specific configuration workaround for LXD other than updating, but the Incus project also highlighted that restricting network access is the only interim step available besides updating. Review firewall rules and network segmentation to ensure the LXD/MicroCloud HTTPS API is only accessible from trusted internal networks or specific management hosts, if absolutely necessary.

Advertisement

Advertisement