The News, Explained
Cloudflare said on September 24, 2026 that it had fixed a vulnerability in Containers and the Sandboxes product built on top of it that could expose residual data from another customer. Cross-tenant exposure means data from one customer becomes visible to another customer sharing the same underlying infrastructure. A security researcher reported the issue on September 4. Source
Why residual data could appear
Containers reuse physical blocks from a storage pool shared by multiple customers. A storage pool is a shared collection of storage capacity, while a physical block is an actual unit where data is stored. With the skip_block_zeroing setting enabled, newly allocated blocks were not zeroed before reuse. Zeroing means overwriting newly assigned storage with zeros so data from an earlier use does not remain. Writing to part of a block and then reading the remaining area could reveal data left by a previous container. Source
In the researcher’s tests, residual data did not appear every time, and the technique could not target a specific victim, workload, or host or access an active disk. Potentially exposed material included filesystem metadata, directory structures, database pages, and application data. Source
Changes Cloudflare made
Cloudflare first removed skip_block_zeroing from the dm-thin pool configuration so newly allocated blocks would be initialized. dm-thin is a Linux thin-provisioning mechanism that allocates physical storage as it is needed. The researcher independently confirmed that the original proof of concept no longer worked after the change. Source
Existing disks and cached image snapshots could still contain old mappings, so Cloudflare also discarded container disks, removed prebuilt image snapshot caches, drained hosts in sequence, and restarted virtual machines. The company said it completed cleanup of cached snapshots from before the mitigation on September 19. Source
Investigation and customer guidance
Cloudflare analyzed historical disk I/O telemetry and said it found no additional activity matching the technique beyond authorized testing by the researcher and Cloudflare engineers. Disk I/O telemetry is operational data about storage read and write activity. It also said it found no evidence of customer data compromise. Source
Cloudflare’s notice says customers do not need to change settings or take additional action. The storage-allocation change and cleanup of existing disks and caches were performed by Cloudflare on the service side. Source
OYOPICK’s Take
Zeroing new allocations and clearing existing disks and caches are separate completion checks. This response changed allocation behavior and then cleaned up earlier snapshots. When reading similar notices, the treatment of storage retaining the old state deserves attention alongside the changed setting.
The finding of no exploitation evidence is bounded by retained historical telemetry. Publishing the cause, researcher revalidation and completion of legacy-data cleanup helps readers assess the response. We hope such disclosures strengthen how shared-infrastructure isolation problems are found and verified.