Quick answers
- Is CVE-2026-112816 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112816 being exploited in the wild.
- How severe is CVE-2026-112816?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Canonical LXD 4.0.14, 5.0.10, 5.21.8, 6.9; Canonical MicroCloud affected versions not specified.
- Is there a fix for CVE-2026-112816?
- Yes: fixed in LXD 4.0.15, 5.0.11, 5.21.9, 6.10.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112816 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-112816?
- Check whether you run Canonical LXD or Canonical MicroCloud at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: LXD 4.0.15, 5.0.11, 5.21.9, 6.10.1
Technical details
The vulnerability is an improper certificate validation flaw in the HTTPS listener that fails to properly verify certificate chains, allowing an unauthenticated network attacker to forge or craft a certificate chain to impersonate any trusted TLS client. This requires network access to the HTTPS API endpoint but no prior authentication or credentials. The attacker can achieve full cluster compromise including access to all managed VMs and containers.
Affected products
- Canonical LXD 4.0.14, 5.0.10, 5.21.8, 6.9
- Canonical MicroCloud affected versions not specified
Timeline
- 2026-10-29: disclosed: Security advisory published by Canonical; vulnerability referred from Incus project
- 2026-10-28: patched: LXD 4.0.15 released with security fixes