Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: containers (2 articles)Clear

Critical LXD and MicroCloud flaw lets attackers impersonate trusted clients without their private key

The Incus project reported, and Canonical confirmed, CVE-2026-112816, a flaw rated 10.0 in LXD and MicroCloud that lets an attacker with network access to the HTTPS API impersonate any trusted client. The server checked each certificate the client sent against the trust store, but a TLS connection only proves the client holds the private key for the leaf certificate, so an attacker can attach a trusted client's non-secret public certificate behind their own and be accepted as that client. Fixes are in LXD 6.10.1, 5.21.9, 5.0.11, and 4.0.15, MicroCloud 3.4.1 and 2.1.5, and Incus 7.6.0. No exploitation is reported, and a standalone LXD server does not expose the API by default.

Check
Upgrade LXD, MicroCloud, or Incus to the fixed release for your branch, and restrict network access to the HTTPS API to trusted management hosts.
Affected
LXD or MicroCloud servers exposing the HTTPS API let an attacker attach a trusted client's public certificate behind their own and be accepted as that client.
Fix
Apply the fixed LXD, MicroCloud, or Incus versions, keep the API off untrusted networks, and review the trust store and API access logs.

Cloudflare fixes Containers flaw that let one customer read another's leftover disk data

Cloudflare fixed a flaw in Cloudflare Containers that let a paying customer read data other customers' containers left behind on the same shared server. Cloudflare Sandboxes, sold for running untrusted code including AI-agent code, was affected too. Each container gets a disk built with Linux thin provisioning in 64-kilobyte blocks; when a container was deleted, its blocks returned to a shared pool set to skip wiping before reuse. A new container writing only a little into a reused block left the rest holding the previous customer's data, though the attacker could not choose whose. Accomplish reported it on September 4, and Cloudflare says no customer action is needed.

Check
No customer action is required since Cloudflare fixed it service-side, but review whether sensitive workloads ran on Cloudflare Containers or Sandboxes during the exposure window.
Affected
Workloads on Cloudflare Containers or Sandboxes could have their freed disk blocks read by a later container on the same shared host before the fix.
Fix
Rely on Cloudflare's service-side fix, and for shared-tenant platforms generally, avoid writing secrets to container disk and rotate any that may have persisted.