Koffei

CVE-2026-112816

🟠 Medium

Canonical LXD, and Incus is affected by the same CVE id although the CVE record lists only LXD. Canonical's advisory of 28/10/2026 also lists MicroCloud, but through a separate certificate-interception issue on cluster join that carries no CVE id of its own, so MicroCloud is not covered by this row · LXD 4.0.14 < 4.0.15 ; 5.0.10 < 5.0.11 ; 5.21.8 < 5.21.9 ; 6.9.0 < 6.10.1 (CVE record). Incus: all releases before 7.6.0, through 7.5.x, per the Incus advisory GHSA-xg75-xf37-cph9 of 29/10/2026

CVSS (Koffei note)
10.0
CVSS (v4.0, CVE List)
10.0
EPSS (2026-11-18)
0.303%
23.48th percentile

Exploitation

No — no exploitation known. SSVC 30/10/2026: exploitation none, automatable yes, technical impact total, and it is not in CISA KEV. Public proof-of-concept code is indexed: four repositories are listed for this CVE by the sploitus aggregator. None was opened, and per Ostorlab the vendor advisories link no proof of concept, so the PoC claim rests on the aggregator's listing rather than on a vendor or researcher publication. The flaw was reported to Canonical by the Incus project and the CVE record credits Stéphane Graber Recheck of 03/11/2026: nothing changed. The record and the EPSS score are unmoved, it is still outside CISA KEV with SSVC reading exploitation none, and no exploitation was found. Corroborated by the Daily CyberNews notes of 02/11 and 03/11/2026, which both list MicroCloud alongside LXD. That agrees with Canonical's advisory ; the advisory attributes MicroCloud's exposure to a separate certificate-interception issue on cluster join rather than to this CVE id, so the scope note above stands.

Timeline

  1. 30/10/2026CVE record published (CVE List)
  2. 02/11/2026Canonical LXD/MicroCloud max-severity auth bypass
  3. 03/11/2026Canonical LXD / MicroCloud — maximum-severity certificate-impersonation flaw

Risk

10.0 Critical (v4.0, Canonical CNA) — AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H, EPSS 0.303% (23.15th percentile, scored 01/11/2026) — no NVD score and no second scorer (CWE-295 improper certificate validation, CAPEC-475 signature spoofing : the HTTPS listener asks for a client certificate chain and does not verify it, then the trust checks compare every certificate the client presented against the trust store rather than the leaf alone. An attacker connects with their own leaf certificate and appends a trusted identity's public certificate to the chain, and is authenticated as that identity, which gives full access to the cluster and to the virtual machines it manages. Unauthenticated, no user interaction)

Fix

Yes — LXD 4.0.15, 5.0.11, 5.21.9 and 6.10.1, each with its own release announcement on the Ubuntu discourse, and Incus 7.6.0 of 30/10/2026. Vendor advisory GHSA-99jp-jwmc-65p4 and Canonical's advisory of 28/10/2026. No workaround is published, and the Canonical page truncated when read, so the fixed versions above come from the CVE record and the Incus advisory rather than from that page

Official description

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.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

CWE-295