The news
Cloudflare disclosed on September 24 a Cloudflare Containers flaw, also affecting Cloudflare Sandboxes, in which a storage configuration could expose residual data from one customer’s workload to another. The issue was reported through its bug bounty programme on September 4 by Oren Yomtov of Accomplish.
According to Cloudflare, the root cause was a Linux storage setting that skipped zeroing disk blocks before reusing them, so fragments of a previous container’s files could remain readable by the next tenant on the same host. The researcher recovered residual material on 18 of 24 container placements. Cloudflare cited database pages and SQLite databases; BleepingComputer reported leftovers could also include browser profiles, .env and credential files, though the researcher’s checks returned only counts, not contents.
Cloudflare said exploitation required a Workers Paid account, an attacker could not choose a target, guarantee what data they would find or access an actively attached disk, and the researcher did not demonstrate modifying other customers’ active data. Its telemetry review found no evidence of malicious exploitation beyond the researcher’s authorised testing.
The company said it removed the setting fleet-wide by September 7, then retired pre-fix container disks and cleared cached image snapshots, finishing cleanup on September 19, 15 days after the report. Cloudflare said customers do not need to take any action.
The numbers
- Reported
- Sept 4, 2026
- Fix rolled out fleet-wide
- Sept 7, 2026
- Cleanup completed
- Sept 19, 2026
- Placements with residual data in testing
- 18 of 24
Why CEOs should care
Multi-tenant cloud services promise isolation between customers, and this case shows that promise can fail at low levels of the stack. Cloudflare fixed it within three days and published a detailed timeline, but leaders should ask their engineering teams whether workloads write secrets, API keys or customer data to local disk, and whether those secrets are rotated regularly.
For vendor risk, add questions to cloud and SaaS reviews: how does the provider sanitise shared storage between tenants, how does it detect cross-tenant access, and how fast has it fixed past isolation bugs? Cloudflare’s three-day fleet-wide fix, with cleanup in 15 days, is a useful benchmark.
The bigger picture
Serverless containers and AI agent sandboxes often run untrusted or customer-supplied code. Isolation flaws in these environments are likely to draw more researcher attention.
What “Fact-checked” means
Fact-checking means testing a story’s facts against the evidence before it is published. This story went through at least two separate checks before this version was published.
- What we checked
- Its names, figures, dates, job titles, quotes and who said what were checked against the story’s sources, including its main source where it could be opened. The headline was checked for accuracy and overstatement.
- How
- A first check reviewed the whole story. If it passed, a second, skeptical check went back to the sources to look for mistakes in the most important facts. If a check flagged the story, it was edited to fix the problems found, and a separate re-check then reviewed the whole story again.
- Who
- The checks are made by our newsroom, as steps kept separate from the writing, under rules set by our editor, Hussein Mukhtar. A story the checks still flag is held for the editor, who decides whether it is fixed, published or dropped.
- If something is wrong
- “Fact-checked” does not mean error-free. If a material error is found after publication, we correct the story and add a note saying what changed. Report an error
Companies in this story








