The lede
How Cloudflare addressed a cross-tenant data exposure vulnerability in Containers
Cloudflare · made the Sunday
A researcher at Accomplish showed that any Workers Paid account could write 4 KiB into a fresh container disk and read back the other 60 KiB of a recycled 64 KiB block — because the storage pools ran dm-thin with `skip_block_zeroing`, a speed choice that quietly turned deleted tenants' data into someone else's free space. Across 24 placements they recovered residual material on 18 of them: directory structures, database pages, other people's filesystems, on nodes across four continents. Cloudflare has fixed it fleet-wide with no customer action needed, and the writeup is the good kind — the exploit steps, the counts, the timeline — but the lesson for anyone shipping on this stack is that Sandboxes is built on Containers, which means the isolation your agents run inside was one config flag deep.