Skip to content
Security

Canonical LXD, CVE-2026-112816: a new CVE scored 10

·9 min read

The bottom line

If you run LXD or MicroCloud, update this week. The vendor calls the flaw critical and released fixes on 29 October 2026. First, check whether anything untrusted can reach the LXD HTTPS API. If you run neither product, stop reading.

At a glance

FactDetail
ProductCanonical LXD (CVE-2026-112816)
SeverityCritical: 10 (CVSS 4.0)
StatusA new CVE record, published by Canonical on 30 October 2026. Not on CISA's list of exploited vulnerabilities when we read it on 6 November 2026, which means nothing public says yet that anyone is using it.
Fixed inlxd 6.10.1, 5.21.9, 5.0.11, 4.0.15; microcloud 2.1.5, 3.4.1 (snap, 29 October 2026)
Who looks firstAnyone running LXD or MicroCloud where the LXD HTTPS API can be reached by people or machines you do not fully trust. The advisory also names MicroCloud clusters where a new member is joining.

Does this apply to you?

Answer in order. Stop at the first no.
QuestionIf noIf yes
Do you run Canonical LXD or MicroCloud, on any host?Nothing to do for this CVE.Check the version (next question).
Is the version older than the fixed releases listed above for its channel?You are on a fixed release. Confirm it in writing.Go to the next question, then patch.
Is the LXD HTTPS API switched on for network access?Exposure is lower, but still patch. The sources do not say this removes the risk.Ask who can reach it (next question).
Can anyone outside your admin team reach that API port?Patch in your normal cycle, but soon.Restrict access now and patch first.

What it is

LXD's HTTPS API checked every certificate a client sent, but only the first one proves the client holds the key. The record says an attacker can put a trusted public certificate in the chain and be treated as that client, gaining full access to the cluster and its virtual machines.

Why it matters

The advisory says that, depending on the victim's privilege, the attacker may gain root access to the host. Our reading is that an LXD host is a good place for an attacker to stand: it controls the virtual machines on it. The attacker needs only a trusted client's public certificate, which is not a secret. The record gives this a score of 10 and the vendor calls it critical, so the fact that CISA does not yet list it should not lower your urgency.

What the vendor's advisory says

We read three pages on discourse.ubuntu.com. In short:

  • The vendor's advisory says an attacker who can reach the LXD HTTPS API can authenticate as any trusted TLS client whose public certificate they hold.
  • In MicroCloud, the advisory says an attacker can intercept the public certificate of a joining cluster member and then authenticate as that member.
  • The advisory says all users must update to the latest version in their channel, using a snap refresh of lxd and of microcloud.
  • The advisory says the point releases were still in progressive roll out from candidate to stable, so your host may not see the fix at once.
  • The advisory says the issue was referred by the Incus project and confirmed to affect LXD as well.

Exposure by situation

These priorities are our judgement from what the sources say about who can use the flaw and how. They are not vendor ratings.

Where you stand, and how soon
Your situationPriorityTimeframe
LXD API reachable from the internet or from untrusted networksHighToday; restrict access, then patch
MicroCloud cluster, especially while a member is joiningHighToday; update microcloud and lxd
LXD API reachable only from a trusted management networkMediumThis week
LXD installed but the HTTPS API not enabled for the networkLowNext patch cycle
No LXD or MicroCloud anywhere in your estateNoneNone for this CVE

Things people will get wrong

  • "It is not on the CISA list, so it can wait." The record is new and CISA has not listed it. The vendor still calls it critical and urges updating immediately.
  • "An attacker needs a login first." The record says the attacker is unauthenticated. The advisory says they need a trusted client's public certificate, which is not secret.
  • "The snap refresh has already fixed us." The advisory says the releases were still rolling out to stable. Check the installed version against the fixed one.

How we would triage it

This is our judgement.

The commands only read: they print a version or list what is installed. They come from general knowledge of this kind of product, not from the sources, so check them against the vendor's page before you run them. Words in capitals are for you to fill in.

Step 1: Find the versions you run

  • List every host running LXD or MicroCloud, since the fix is per channel and each snap needs its own update.
  • Compare each version with the fixed releases for its channel.
snap list lxd microcloud
lxd --version
snap info lxd

Step 2: Reduce exposure

  • Find out whether the HTTPS API listens on the network and who can reach it.
  • Limit that access to named administrator machines until the patch is in.
lxc config get core.https_address

Step 3: Patch

  • The vendor's advisory says to run a snap refresh for lxd and for microcloud.
  • If your channel has not received the fix yet, note it and check again, because the roll out was progressive.

Step 4: Check the result

  • Confirm each host now reports a fixed version.
  • Review client certificates the cluster trusts and remove any you do not recognise.
lxc config trust list

To close it, read the version from the product itself, not from an old inventory, and save the output with the date. If you cannot update today, write down who owns it, the new date, and what limits exposure until then.

Send this to your IT provider

Copy it, change the names and dates, and send it. It is a draft for you to check, not a template tested with any provider.

Hello, we need to know whether we run Canonical LXD or MicroCloud, and where. The vendor has published a critical flaw, CVE-2026-112816, in how the LXD HTTPS API checks client certificates. Please tell us which hosts run either product, which version each uses, and whether the HTTPS API can be reached from outside our admin network. The fixed versions are lxd 6.10.1, 5.21.9, 5.0.11 or 4.0.15, and microcloud 2.1.5 or 3.4.1. Please confirm in writing the installed versions and that the fix is applied, by the end of this week.

The weakness behind it

The record classes this as CWE-295.

Likely ATT&CK mapping

MITRE ATT&CK is a public catalogue of the steps attackers take, from getting in to causing damage. No source has mapped this flaw to it yet, so the steps below are our prediction from what the record says the flaw allows. They are not MITRE's, the vendor's or CISA's, and an attacker may do other things.

Steps an attacker would likely take with this flaw
The step, in plain wordsStage of an attackWhy we think so
Exploitation of Remote Services (T1210): Exploiting a flaw in a service on another machine to move to it.Lateral Movement: moving to other machinesOnce an attacker has network access to the LXD HTTPS API, the certificate chain manipulation would likely allow lateral movement into cluster nodes and managed VMs by exploiting this remote service's authentication logic.
Exploitation for Privilege Escalation (T1068): Using a flaw to gain higher rights than the account had, such as administrator or root.Privilege Escalation: gaining higher rightsThe advisory notes that depending on the victim identity impersonated, an attacker could gain root access to the host machine, suggesting successful exploitation would typically lead to privilege escalation beyond the initial API access.

How to use this: ask your IT provider which control or log would show each step, for example whether sign-in attempts from the internet are recorded. If nobody can answer, that is the gap to close first.

MITRE ATT&CK® is a registered trademark of The MITRE Corporation. Technique names are MITRE's.

The sources, in their words

The CVE record:

Improper certificate validation in the HTTPS listener in Canonical LXD 4.0.14, 5.0.10, 5.21.8, 6.9 before 4.0.15, 5.0.11, 5.21.9, 6.10.1 allows an unauthenticated attacker to authenticate as any trusted client and gain full access to the cluster and managed virtual machines via a crafted certificate chain.

Versions of Canonical LXD the record lists as affected:

  • 4.0.14 up to, but not including, 4.0.15
  • 5.0.10 up to, but not including, 5.0.11
  • 5.21.8 up to, but not including, 5.21.9
  • 6.9.0 up to, but not including, 6.10.1

The record gives no version ranges. Use the vendor's advisory for the affected versions.

Check your own project

If you build software, you can compare what a project declares with this CVE from a terminal. The tool reads requirements files, package.json, Maven, Gradle, Cargo, CMake and Dockerfile files, runs nothing, and only the CVE id leaves your machine. Naming the CVEs needs no key.

lattice-scan project . --cve CVE-2026-112816

Each row says in-range, outside-range, undetermined or lead, with the file and line. That is evidence about what a manifest declares, not about what runs, and a person decides. The verdicts, the CSV columns and a pipeline recipe are in the guide.

Check the servers you run

The same id can be checked against a host. Run this on the machine itself, not on the laptop that deploys to it: it reads installed packages (dpkg, rpm or apk), snaps, the hardware, the running container images with their operating system and packages, and the kernel version, compares them on the spot, and only the CVE ids leave the machine; the inventory stays on it, in ~/.lattice-scan. Naming the CVEs needs no key. Do it on each server after a deployment, and again when a new entry lands.

lattice-scan --cve CVE-2026-112816

A match is a candidate for a person to confirm, not a finding. A distribution can fix a CVE under an unchanged version number, so a match is a candidate; on Debian-family hosts the report also shows whether the package's own changelog names the CVE. It reads the names of the running images, not what is inside them; for what an image declares, use the project check on its Dockerfile.

Guide: namiq.io/lattice/guides/choose-your-channel. MCP server (io.namiq/lattice in the MCP registry): namiq.io/lattice. Package: pypi.org/project/lattice-scan, or namiq.io/apt.

What we do not know yet

  • Whether the flaw is being used against real systems; CISA does not list it and the sources do not say.
  • Whether turning off the network HTTPS API removes the risk; the sources do not say.
  • Whether the fix has reached the stable channel for each release; the advisory says roll out was in progress.
  • Whether the weakness leaves visible traces in logs; the sources do not say.
  • Exploitation is not recorded. That is not the same as none.
  • This is a new record: scores, versions and wording can change in the first days, and they are as at 6 November 2026. We read the vendor pages listed under Sources; nothing here has been tested.
  • The sections headed "The bottom line", "Does this apply to you?", "What it is", "Why it matters", "Exposure by situation", "Things people will get wrong", "Likely ATT&CK mapping", "How we would triage it" and "Send this to your IT provider" are our interpretation of the sources, not a statement by CISA or the vendor.

Does this touch your business?

A new vulnerability is a question about what you run, who can reach it and what it would cost you. If you want a person to answer it for your own systems, start with your IT setup.

Also worth reading

Start with one piece of work.

Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.

Talk to us