Cloudflare Patches Multi-Tenant Storage Remanence in Edge Container Fleet

Security researchers at Accomplish uncovered a cross-tenant data exposure vulnerability in Cloudflare Containers and Cloudflare Sandboxes, which run multi-tenant containerized workloads across Cloudflare's distributed edge network. The underlying container runtime utilizes Linux device mapper thin provisioning (dm-thin) to allocate 64 KiB storage blocks on demand for writable root filesystems presented via Firecracker microVMs. When new workloads were provisioned on hosts where previous containers had executed, thin-provisioned storage pools failed to completely zero out unmapped blocks, allowing a tenant on a shared host to reconstruct residual filesystem structures and foreign inodes. Cloudflare patched the issue across its entire global fleet without requiring customer intervention or configuration updates. For platform engineers and DevOps architects, this vulnerability exposes a critical gap in edge computing isolation models. While runtime sandboxing technologies like microVMs, kernel namespaces, and eBPF-driven network filters provide strong process and network boundary enforcement, storage remanence at the virtual block layer bypasses these perimeter controls entirely. Even without direct network lateral movement or guest kernel breakouts, an attacker operating within a standard multi-tenant environment could passively inspect reallocated disk blocks, potentially harvesting stale authentication keys, TLS certificates, cached credentials, or private configuration payloads left behind by preceding workloads. This incident mirrors broader challenges in modern edge networking and serverless container paradigms. As providers race to minimize cold-start latency and reduce storage overhead through dynamic thin provisioning and rapid container recycling, the lifecycle management of underlying storage devices becomes an overlooked attack vector. Hyperscalers and distributed edge providers frequently optimize storage layers by skipping immediate block sanitization in favor of asynchronous re-allocation. However, as shown by this discovery, cryptographic filesystem validation techniques—such as ext4 metadata checksum analysis—can easily identify cross-tenant block leakage. Practitioners operating or consuming multi-tenant container platforms should treat ephemeral disk storage as potentially vulnerable unless cryptographically wiped or isolated at the encryption key level. While Cloudflare's fleet-wide patch enforces complete block zeroing between tenant reallocations, teams building private multi-tenant container fabrics should audit their own storage drivers, utilize per-workload ephemeral encryption keys (such as dm-crypt with disposable keys), and ensure that automated CI/CD and sandbox environments explicitly wipe local scratch spaces on teardown.