Cloudflare has disclosed and remediated a cross-tenant data exposure vulnerability in Cloudflare Containers, its platform for running containerized workloads at the edge. The issue was reported by external security researchers at Accomplish, who found that residual disk data from a previous workload could potentially be exposed to a subsequent tenant. Because Containers share underlying infrastructure across customers, any leakage between workloads carries multi-tenant risk, so Cloudflare investigated how the exposure occurred and shipped fixes to close it.
- Investigated how residual disk data from prior workloads could persist and become readable by later tenants sharing the same container infrastructure.
- Remediated the exposure path so that data from a previous workload's disk is no longer accessible to subsequent workloads on the platform.
- Credited the external researchers at Accomplish, who identified and reported the vulnerability.
- Published a transparent write-up covering how the issue worked, how Cloudflare investigated it, and the remediation steps taken.
For developers building on Cloudflare Containers, the disclosure highlights the tenant-isolation guarantees that underpin multi-tenant platforms. Workloads often handle sensitive data—API keys, user records, generated artifacts—and any residual storage leaking across tenants undermines that boundary, raising both security and compliance concerns. Cloudflare's response is a reminder that isolation must be enforced at every layer, including ephemeral disk. Teams running Containers should review how their workloads handle sensitive data, confirm they are using supported platform configurations, and monitor Cloudflare's advisories. The prompt investigation and public write-up also reflect the value of external security research and coordinated disclosure in catching issues that internal testing may miss.
Source: https://blog.cloudflare.com/containers-cross-tenant-vulnerability/