Cloudflare has addressed a cross-tenant data exposure vulnerability in its Containers platform, affecting global multi-tenant cloud computing infrastructure This article explores cloudflare noted vulnerability. . Cloudflare also noted that this vulnerability impacted Cloudflare Sandboxes, built on Containers, but found no evidence of malicious exploitation or customer data compromise in retained telemetry.
Oren Yomtov, a security researcher at Accomplish, responsibly disclosed the flaw through Cloudflare’s HackerOne bug bounty program on September 4, 2026. Exploitation required a Workers Paid account, and Cloudflare’s automatic workload placement meant an attacker could not choose a victim, host, workload, or specific information. Despite the limitations, exposed fragments might still include filesystem metadata, application details, or sensitive database content.
This change did not sanitize blocks already mapped into running disks or cached OCI image snapshots, so the company also retired existing container disks, drained hosts, restarted virtual machines, and cleared image caches. Cloudflare then developed detection signatures around the attack’s unusual disk I/O pattern: small 4 KiB writes followed by substantially larger reads from newly allocated 64 KiB blocks. The widespread remediation process requires no customer configuration changes, but organizations should evaluate whether secrets in affected workloads need to be rotated according to their own risk policies.
SOC alert investigations can be reduced by 21 minutes, and the integration of TI Lookup into your SOC can provide instant IOC context for swift response.












