CVE-2026-99999, nicknamed PwnEscape, scores 9.3 and sits in the IPv4 checksum code every host kernel runs. Fixed stable kernels range from 5.10.272 to 7.2.11.
LXD and MicroCloud fix a flaw that lets a public certificate log in
EditorialBy TrustList Editorial
CVE-2026-112816 lets anyone who can reach the API and holds a trusted client's public certificate act as that client, up to root on the host. Fixed snaps went out on 29 October.
- Linux
- Virtualization
- DevOps
- Cybersecurity
About LXD and MicroCloud fix a flaw that lets a public certificate log in
LXD and MicroCloud fix a flaw that lets a public certificate log in
28 October 2026: Canonical has fixed CVE-2026-112816, a critical authentication bypass in LXD and MicroCloud that lets an attacker who can reach the LXD HTTPS API authenticate as any trusted TLS client whose public certificate they hold, and so gain root on the host if that client is privileged. Canonical published no workaround: every user is told to refresh the snaps now.
Update, 13 November 2026: Canonical, as the numbering authority, published the CVE record on 30 October 2026. It scores the flaw 10.0 (Critical) under CVSS 4.0 and lists the fixes in 4.0.15, 5.0.11, 5.21.9 and 6.10.1. CISA's added assessment of 30 October records no known exploitation and rates the flaw automatable.
How a public certificate became enough
LXD authenticates remote clients with mutual TLS. Canonical's advisory says the daemon compared every certificate the client sent against its trust store, when only the leaf certificate proves that the client holds the matching private key. An attacker could therefore send their own certificate as the leaf and slip a trusted client's public certificate into the chain as an intermediate, and LXD would accept the connection as that trusted client.
Public certificates are not secrets. They sit in configuration files, cluster join records and backups, so the only real barrier was network reach to the API.
MicroCloud has a second route to the same result. Canonical says an attacker can intercept the public TLS certificate of a member joining a cluster and then authenticate as that member once it has joined.
The flaw was referred to Canonical by the Incus project, the community fork of LXD, and Canonical confirmed that LXD is affected as well.
Fixed snap versions
Canonical lists these fixed builds, all released on 29 October:
| Channel | Snap | Fixed version |
|---|---|---|
| 6/stable | lxd | 6.10.1 |
| 5.21/stable | lxd | 5.21.9 |
| 5.0/stable | lxd | 5.0.11 |
| 4.0/stable | lxd | 4.0.15 |
| 3/stable | microcloud | 3.4.1 |
| 2/stable | microcloud | 2.1.5 |
The update is sudo snap refresh lxd and sudo snap refresh microcloud. Canonical notes that the LXD point releases were "in progressive roll out from candidate to stable" when it posted, so a host that refreshed early on 29 October may still be on the old build. Check the installed version with snap list lxd rather than trusting the refresh.
Who is most exposed
The risk is highest where the LXD API listens on a network address, which is the normal setup for clusters, remote management and any tooling that drives LXD over HTTPS. A host that only accepts the local Unix socket is not reachable this way. Long-lived 4.0 and 5.0 hosts deserve a direct look, since snaps pinned to an old track or held back from automatic refresh will not pick up the fix on their own.
After patching, review the trust store with lxc config trust list and remove clients nobody recognises, and look in the LXD logs for API sessions from addresses that do not belong to known management hosts. Canonical has not said whether the flaw has been used in attacks.
Our virtualization category lists 14 products for teams comparing container and virtual machine platforms.
Company profile on TrustList: Canonical
Related on TrustList:
- Linux TCP flaw CVE-2026-98432: Debian and RHEL 8 fixed, others waiting
- Linux kernel flaw lets a guest VM read and crash its host
- XSA-523: two grant copy flaws let a Xen guest read and write Dom0 memory
Sources
- Canonical (Ubuntu Discourse): Security advisory: Critical vulnerability found in Canonical LXD and MicroCloud, 28 October 2026
- CVE Program: CVE-2026-112816, 30 October 2026
Categories & features
- Linux
- Virtualization
- DevOps
- Cybersecurity
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
CVE-2026-111497 is rated 9.2 by Google and hits every Brotli release from 1.0.3 to 1.2.0. Envoy, the PyPI packages and Debian have shipped fixes; Ubuntu still ranks it medium.
Every musl release from 0.5.0 to 1.2.6 is affected. The maintainers ship a patch now and say 1.2.7 will follow; only programs that compile regular expressions from untrusted input are exposed.
Packages for those minor releases, including PostgreSQL 18, move to the YUM archive and get no further updates; servers on RHEL, Rocky Linux or AlmaLinux 10.0 or 9.6 should move to a newer minor release.
Heroku repeated the deadline alongside a 20 October update to all three stacks; buildpack apps get fixes automatically, but apps on the container stack must rebuild their Docker images.
The Linux kernel ESP page-cache flaw CVE-2026-46300, which CISA says can be chained to plant PHP webshells as root, is due by 31 October; VMware ESX CVE-2026-41709, which lets an administrator act unlogged, by 11 November.
The Grenoble maker of the XCP-ng and Xen Orchestra virtualisation software says it has been profitable since 2016, that the founders keep the majority and that both products stay open source.
Amazon Linux 2 and 2023 kernels are out now. EKS and ECS AMIs dated 31 October carry the fix, Redshift follows on 2 November and RDS and Aurora on 3 November.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More LinuxThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.