1. Executive Summary & Vulnerability Overview
Canonical and the upstream container community have disclosed a critical authentication bypass vulnerability (CVE-2026-112816) affecting Canonical LXD, MicroCloud, and the community fork Incus. Assigned a maximum severity rating of CVSS v4.0 10.0 (Critical), this flaw resides in how the HTTPS API listener validates client certificate chains during mutual TLS (mTLS) authentication.
When the LXD or MicroCloud HTTPS listener is reachable over the network, a remote attacker can bypass authentication without possessing a valid private key. By presenting a self-signed leaf certificate alongside the public TLS certificate of any trusted client in the certificate chain, an attacker can impersonate that trusted identity. On systems where the impersonated client holds administrative privileges, successful exploitation grants immediate root-level control over the host operating system and all guest instances.
Engineering teams operating container clusters or private clouds on LuckVM Hong Kong CN2 GIA Cloud VPS, US Cloud VPS, or Bare Metal Bulk-IP Proxmox / VMware Hosts should immediately audit their snap revisions, take pre-upgrade snapshots, and restrict management plane exposure.
2. Technical Root Cause: How mTLS Authentication is Bypassed Without a Private Key
In a compliant mutual TLS (mTLS) implementation, the server must strictly bind the authenticated session identity to the leaf certificate (the first certificate in the chain), for which the client cryptographically proves possession of the corresponding private key during the TLS handshake.
In affected versions of LXD, MicroCloud, and Incus, the certificate verification logic improperly iterated through the entire user-supplied certificate chain. If any intermediate certificate appended to the chain matched an entry in the server's local trust store, the server treated the connection as authenticated:
-
Exposed LXD API Nodes: An attacker can generate an arbitrary self-signed leaf certificate to complete the TLS handshake and append a known public certificate of a trusted LXD client as an intermediate certificate. The LXD daemon matches the appended public certificate against its trust store and grants full API access under that client's permissions.
-
MicroCloud Clusters: During cluster join operations, if an attacker can observe or obtain the public TLS certificate of a joining node, they can replay that public certificate in a crafted chain to impersonate a legitimate cluster member and compromise the cluster.
3. Exposure Preconditions & Affected Version Matrix
A server running LXD is only vulnerable to remote exploitation if both of the following preconditions are met:
-
Network-Exposed HTTPS API: The LXD daemon is configured to listen on a network interface (typically TCP port
8443). By default, standalone LXD installations only listen on a local Unix socket and are not exposed to the network unlesscore.https_addresshas been explicitly set or clustering/MicroCloud is enabled. -
Knowledge of a Trusted Public Certificate: The attacker must possess the public certificate (which is not secret by design) of a client or cluster member already registered in the server's trust store.
Below is the complete matrix of affected versions and official patched releases (note that Ubuntu archive .deb packages are unaffected; remediation applies to Snap packages and upstream releases):
| Software Component | Vulnerable Versions | Patched Version (Safe) | Distribution Channel |
| Canonical LXD (6.x Series) | |
6.10.1 or later |
Snap latest/stable channel |
| Canonical LXD (5.21 LTS) | |
5.21.9 or later |
Snap 5.21/stable channel |
| Canonical LXD (5.0 LTS) | |
5.0.11 or later |
Snap 5.0/stable channel |
| Canonical LXD (4.0 LTS) | |
4.0.15 or later |
Snap 4.0/stable channel |
| Canonical MicroCloud | 2.x & |
2.1.5 (2/stable) / 3.4.1 (3/stable) |
Snap stable channels |
| Incus (Upstream Fork) | |
7.6.0 or later |
Distribution packages & source |
4. 4-Step Production Remediation & Hardening Guide
Step 1: Create an Instance Snapshot or Host Backup Before Patching Before applying runtime updates to production nodes, protect your workload state. If you are running on a LuckVM Cloud VPS, log in to the LuckVM Web Control Panel and trigger a one-click Snapshot Backup for instant rollback capability. If you are managing a LuckVM Bare Metal Dedicated Server or Proxmox Host, verify your hardware RAID10 array health and export your container configuration metadata prior to maintenance.
Step 2: Audit Current Versions and Network Exposure Connect to your instance via SSH or the out-of-band LuckVM VNC Emergency Console and inspect your installed snap revisions and listening sockets:
# 1. Check installed LXD and MicroCloud snap versions
snap list lxd microcloud
# 2. Verify whether the HTTPS API is bound to a network interface (empty output = local Unix socket only)
lxc config get core.https_address
# 3. Inspect active TCP listeners on port 8443
sudo ss -tulpn | grep 8443
Step 3: Refresh Snap Packages and Verify the Installed Revision
Execute the following commands to pull the patched releases immediately:
# Refresh LXD and MicroCloud snaps
sudo snap refresh lxd
sudo snap refresh microcloud
# For Incus deployments, upgrade via your system package manager
sudo apt update && sudo apt install --only-upgrade incus
Important Operational Note: Because Canonical rolls out point releases progressively from candidate to stable channels, do not assume a single refresh command has updated your node. Re-run snap list lxd after refreshing to confirm the revision explicitly shows 6.10.1, 5.21.9, 5.0.11, or 4.0.15. If the progressive rollout has not yet reached your node on stable, explicitly pull from the candidate channel (e.g., sudo snap refresh lxd --channel=5.21/candidate).
Step 4: Restrict Management Plane Exposure and Rotate Certificates
-
Disable Unnecessary Network Listeners: On standalone hosts that do not require remote API orchestration, remove the network listener so LXD only communicates over the local Unix socket:
lxc config unset core.https_address
-
Enforce Strict Firewall and VLAN Boundaries: For multi-node clusters where
core.https_addressmust remain active, never expose TCP port8443to0.0.0.0/0on the public internet. Bind the listener exclusively to an isolated private VLAN interface or restrict ingress viaufw/iptablesto known cluster peers. Should a firewall rule accidentally lock out your SSH session, you can always recover access immediately using LuckVM's out-of-band VNC Console (on Cloud VPS) or dedicated IPMI/iDRAC interface (on Bare Metal hosts). -
Audit and Rotate Trusted Client Certificates: If your API port was previously exposed to the public internet, review all trusted certificates via
lxc config trust listand revoke/re-issue any client certificates whose public keys may have been exposed in logs, repositories, or untrusted networks.
5. Infrastructure Recommendations: Hardware-Isolated Multi-Tenant Virtualization
For engineering teams operating multi-store e-commerce environments, APAC SaaS platforms, or VPS reseller infrastructure, relying solely on shared-kernel containers increases the blast radius of daemon-level vulnerabilities. LuckVM provides hardware-isolated compute options across 40+ global data centers:
-
Isolated KVM Cloud Instances: Deploy on LuckVM Hong Kong CN2 GIA Cloud VPS ($8.80/mo), Tokyo Cloud VPS ($11.00/mo), or Los Angeles Cloud VPS ($8.80/mo) with full KVM hypervisor isolation, 70GB+ NVMe SSD storage (
>3000 MB/s), unmetered bandwidth, and one-click snapshots. -
Single-Tenant Bulk-IP Proxmox & VMware Hosts: Consolidate 10 to 50 isolated virtual machines on LuckVM Bare Metal Bulk-IP Proxmox / VMware Hosts (featuring 22-core Xeon E5 up to 80-core Dual Xeon Gold CPUs, 512GB DDR4 ECC RAM, 8×1TB SSD RAID10, full Root/BIOS/IPMI control, and bulk C-class IPv4 subnets), reducing per-instance infrastructure costs by over 70% while maintaining strict tenant network isolation.
LuckVM Infrastructure & Security Team
![[Security Advisory] Out-of-Band Critical JSSE Vulnerability in Oracle Java SE, GraalVM & OpenJDK (CVE-2026-91403, CVSS 9.1): Fix Guide](https://www.luckvm.com/upload/common/default/b86745c7d3326f2e3c4d19d34984fc95b5cf02df36064e54%5EImage_l3cwyxl3cwyxl3cw.png)

![[Security Advisory] Critical PHP Core RCE Vulnerabilities (CVE-2026-109618 & CVE-2026-109619 / "php2shell", CVSS 9.2) — Impact & Remediation Plan](https://www.luckvm.com/upload/common/default/e1b9b141ed19329fb466078df66762ac62541b57b5d33595%5Eb09788b6-f5eb-4a79-b063-805aa9cd0b82.png)