Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

LXD CVE-2026-112816 and Incus CVE-2026-130778 Certificate Chain Bypass

CVE-2026-112816 is a critical authentication bypass in the HTTPS API of Canonical LXD and MicroCloud.

Reviewed by
Brandefense Analyst Team
Published
Updated
Reading Time
6 min read
CVE ID
CVE-2026-112816
Vendor
Canonical
Affected Product
Canonical LXD 4.0, 5.0, 5.21 and 6 tracks; MicroCloud 2 and 3
Exploitation
Not confirmed
Published
28 October 2026 (Canonical advisory); CVE record 30 October 2026

A client that reaches the API and has a trusted client’s public certificate can authenticate as that client. Canonical rates it CVSS 4.0 10.0 and lists LXD 6.10.1, 5.21.9, 5.0.11 and 4.0.15 as fixes. Canonical says the LXD flaw was reported from the Incus advisory. Incus tracks the same certificate-chain flaw as CVE-2026-130778 and fixes it in 7.6.0. These are distinct CVE records for the two products.

What it allows

The CVE record says improper certificate validation in the LXD HTTPS listener lets an unauthenticated attacker "authenticate as any trusted client." The attacker then gains full access to the cluster and its managed virtual machines. Canonical, the CVE numbering authority, rates it CVSS 4.0 10.0 Critical.

LXD is Canonical's open source container and virtual machine manager. Remote clients sign in to its HTTPS API with mutual TLS, so the client also presents a certificate. LXD then looks for that certificate in its trust store.

How the Bypass Works

Canonical says LXD compared every certificate the client sent with its trust store. Only the first one, the leaf, proves that the client holds the matching private key. An attacker could add a trusted client's public certificate further down the chain and be accepted as that client.

A public certificate is not a secret. Canonical says the attacker needs only that public part and network access to the HTTPS API. Depending on the rights of the impersonated client, Canonical says the attacker may gain root access to the host machine.

MicroCloud, Canonical's LXD-based cloud platform, has a second route. Canonical says an attacker can intercept the public certificate of a member that joins a cluster. The attacker can then authenticate as that member.

How Do LXD CVE-2026-112816 and Incus CVE-2026-130778 Relate?

Canonical's LXD advisory says its finding was reported from the Incus advisory. Both vendors describe a certificate-chain check that trusted a public certificate beyond the first certificate proven by the TLS handshake. Canonical assigns its LXD and MicroCloud issue CVE-2026-112816.

The Incus CVE record assigns CVE-2026-130778 to the Incus implementation and lists versions before 7.6.0 as affected. Its separate Incus CVE-2026-130778 profile covers the Incus fix and authorization impact. Track both product versions independently; the two CVE IDs are related records, not interchangeable product identifiers.

Canonical's now-public advisory confirms that the LXD issue also reaches metrics, cluster and database gateway checks, certificate self-service checks, enrollment and the virtual-machine agent connection. Incus additionally describes an authorization-scriptlet effect, including for token or OIDC clients. That Incus-specific point is not stated in Canonical's LXD advisory.

Is the HTTPS Listener On by Default?

No. LXD's documentation says that by default it "can be used only by local users through a Unix socket and is not accessible over the network." The HTTPS API starts listening once an admin sets core.https_address. By that documentation, a standalone host that never set it has no listener to attack.

Remote clients and the LXD web UI need the listener, and the documentation says the UI "requires LXD to be exposed to the network." Clustered setups also carry traffic over the network through cluster.https_address. Check each host before you treat it as safe.

Research Mentions and Exploitation Status

Brandefense Blackhole counted six dark-chat posts matching CVE-2026-112816 and one matching CVE-2026-130778 from 21 August to 19 November 2026. These per-CVE counts may overlap and should not be added. A general GitHub repository search for CVE-2026-112816 OR CVE-2026-130778 returned three public repository results on 18 November 2026; their contents were not assessed.

LXD and Incus CVE research mentions
Exploit signals
  • Brandefense Blackhole, CVE-2026-112816Yes6 dark-chat posts, 21 Aug to 19 Nov 202619 Nov 2026
  • Brandefense Blackhole, CVE-2026-130778Yes1 dark-chat post, 21 Aug to 19 Nov 202619 Nov 2026
  • GitHub repository search, both CVEsYes3 public results for the two-CVE query; contents not assessed18 Nov 2026
Verdict Prioritize reachable HTTPS listeners and vendor fixes

Mentions and repository search results do not establish an incident or active exploitation. The 18 November 2026 CISA KEV catalog snapshot in the source pack did not list either CVE. Assess exposure and patch status separately for LXD, MicroCloud and Incus.

Other recent flaws also let attackers skip the login on a management interface, such as the Cisco SD-WAN authentication bypass. Our certificate authority glossary entry explains how certificate chains are meant to work.

LXD also shipped fixes for six separate image and snapshot handling flaws reported from the Incus project; see the LXD and Incus image vulnerabilities, six advisories explained.

Who is affected

Canonical's LXD advisory says the certificate-chain flaw has existed since LXD's initial release. The Canonical CNA record separately enumerates four affected LXD version ranges. The table reports those CNA entries and the dated snap-channel observations; the CNA list does not capture the full historical scope described by the advisory.

LXD and MicroCloud version guidance
TrackCNA recordFixed releaseSnap stable channel on 31 Oct
LXD 6 LTS6.9.0 to before 6.10.1 (CNA)6.10.1 for 6/stable6/stable served 6.10.1
LXD 5.21 LTS5.21.8 to before 5.21.95.21.95.21/stable served 5.21.8
LXD 5.0 LTS5.0.10 to before 5.0.115.0.115.0/stable served 5.0.10
LXD 4.0 LTS4.0.14 to before 4.0.154.0.154.0/stable served 4.0.14
MicroCloud 3Not listed in LXD CNA; affected per Canonical3.4.13/stable served 3.4.1
MicroCloud 2Not listed in LXD CNA; affected per Canonical2.1.52/stable served 2.1.5

Sources differ on LXD 6.10.0. Canonical's LXD GHSA lists 6.10.0 and 6.10.1 as patched versions. The Canonical CNA record marks 6.9.0 to before 6.10.1 as affected, which includes 6.10.0. Canonical's snap advisory identifies 6.10.1 as the fixed version for 6/stable. These publications do not establish one agreed status for 6.10.0; update 6/stable to at least Canonical's listed 6.10.1 fix and verify the installed version.

For the 5.21, 5.0 and 4.0 tracks, the CNA record starts at the newest release before each fix. Canonical's LXD GHSA explicitly says the flaw has existed since LXD's initial release. That vendor statement covers older LXD releases beyond the four version ranges individually enumerated by the CNA.

When we checked the Snap Store at 02:12 UTC on 31 October, the 5.21, 5.0 and 4.0 stable channels still served the vulnerable builds. The fixed builds were on the candidate channels. Canonical says all LXD point releases are in "progressive roll out from candidate to stable."

The Snapcraft documentation says snaps update on their own, four times a day by default. A refresh hold can delay that by up to 90 days. A host with a hold, or on the 5.21, 5.0 or 4.0 track, may stay vulnerable until someone checks it.

Ubuntu's CVE page lists the lxd deb package as not affected or not in release for every Ubuntu version. Canonical's fix instructions use snap refresh, not apt. Ubuntu gives the issue Medium priority, while the CNA score is 10.0. Our vulnerability management guide covers how to plan and check a rollout.

Timeline

  1. 19 Oct 2026

    Canonical reserves CVE-2026-112816.

  2. 28 Oct 2026

    LXD 6.10.1 appears on GitHub, and Canonical posts its security advisory for LXD and MicroCloud on Ubuntu Discourse.

  3. 29 Oct 2026

    LXD 5.21.9, 5.0.11 and 4.0.15 appear on GitHub. Canonical lists 29 October as the date of every fixed snap. Incus publishes advisory GHSA-xg75-xf37-cph9.

  4. 30 Oct 2026

    The CVE record and the NVD entry go public. CISA's SSVC entry records exploitation as none.

  5. 31 Oct 2026

    Our Snap Store check finds the 5.21, 5.0 and 4.0 stable channels still on vulnerable builds. The CVE is not in CISA KEV.

What to do

  1. Refresh the LXD and MicroCloud Snaps

    Run sudo snap refresh lxd and sudo snap refresh microcloud, as Canonical advises. Then check snap list for LXD 6.10.1, 5.21.9, 5.0.11 or 4.0.15, or MicroCloud 3.4.1 or 2.1.5.

  2. Find Hosts With the HTTPS API On

    Check core.https_address on every LXD host, plus cluster.https_address on cluster members. LXD's documentation says the network listener runs only once core.https_address is set.

  3. Limit Who Can Reach the HTTPS API

    Until the fixed build is installed, allow the API only from trusted management hosts. Incus gives this advice for its copy of the flaw and says no setting fixes it.

  4. Watch the 5.21, 5.0 and 4.0 Stable Channels

    If snap list still shows 5.21.8, 5.0.10 or 4.0.14, the fix has not reached that host yet. Check again, and lift any refresh hold that blocks the update.

  5. Review the Trust Store

    Remove client certificates the server no longer needs to trust. Canonical says how much an attacker gains depends on the rights of the client it impersonates.

What Brandefense can do

Frequently Asked Questions

Is CVE-2026-112816 exploited?

The 18 November 2026 CISA KEV catalog snapshot did not list CVE-2026-112816 or the related Incus CVE-2026-130778. Canonical’s advisory does not discuss exploitation. These dated observations do not establish whether exploitation has occurred.

Is my LXD host exposed by default?

Not over the network. LXD's documentation says a default install listens only on a local Unix socket. The flaw needs the HTTPS API, which listens once core.https_address is set.

Does snap auto-refresh fix it?

On the 6 track it should, because 6/stable served 6.10.1 on 31 October. The 5.21, 5.0 and 4.0 stable channels still served vulnerable builds then. Check each host with snap list.

Is MicroCloud affected?

Yes. Canonical says an attacker can intercept a joining member's public certificate and then sign in as that member. The fixed MicroCloud versions are 3.4.1 and 2.1.5.

How is Incus CVE-2026-130778 related to LXD CVE-2026-112816?

Canonical says its LXD issue was reported from the Incus advisory. Both describe the same certificate-chain validation flaw, but they are separate CVE records for different products. Update LXD to the fixed release on its track and Incus to 7.6.0 or later.

Sources

  1. Security advisory: Critical vulnerability found in Canonical LXD and MicroCloudCanonical (Ubuntu Discourse)
  2. CVE-2026-112816 RecordCVE Program / Canonical CNA
  3. Authentication bypass through unverified client certificate chainsCanonical LXD
  4. Authentication and authorization bypass through unverified client certificate chains (GHSA-xg75-xf37-cph9)Incus project
  5. CVE-2026-130778 RecordCVE Program / VulnCheck CNA
  6. How to expose LXD to the networkCanonical LXD documentation
  7. Manage updatesSnapcraft documentation
  8. Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →