Cybersecurity
Cloudflare fixes cross-tenant data flaw in Containers
Cloudflare said a storage bug in Containers and Sandboxes could have let Workers Paid customers recover leftover data from other tenants’ containers on the same host, but it found no evidence of exposure.
- Cloudflare said it fixed a vulnerability in Containers and Sandboxes on the Workers Paid plan.
- The flaw could let a customer recover residual data from other customers’ containers on the same physical host.
- Oren Yomtov of Accomplish reported the issue through HackerOne on 4 September.
- Cloudflare said the problem was in a shared storage pool that reused 64 KiB blocks without zeroing them first.
- Cloudflare said it removed the setting, retired existing container disks, cleared cached snapshots, and found no evidence that customer data had been exposed.
Cloudflare said it fixed a vulnerability in Containers and Sandboxes that affected customers on the Workers Paid plan. The issue could have let one customer recover leftover data from another customer’s container on the same physical host.
The report reached Cloudflare through HackerOne on 4 September and came from Oren Yomtov, a security researcher at Accomplish. Cloudflare said the fault lay in a shared storage pool that reused 64 KiB blocks without clearing them first.
According to Cloudflare, a write of 4 KiB to unused space in a new container could leave the rest of a reused block readable. The company said this could expose files such as directory listings, SQLite data, Chromium profiles, environment files and credential files.
Cloudflare said its researchers saw residual material on 18 of 24 container placements and on 20 of 22 underlying nodes. It also said the researchers did not obtain real customer data, and did not show that they could alter another customer’s data or disrupt workloads.
Cloudflare said it removed the setting that skipped zeroing, retired container disks and cleared cached snapshots, finishing the work by 19 September 2026. It said it found no evidence that customer data had been exposed through the method described, and that customers did not need to take any action.
Named in this story
People
- Oren Yomtov
- reported the flaw through HackerOne
Companies
- Cloudflare
- fixed the flaw and disclosed the findings
- Accomplish
- the technology company employing Yomtov
- HackerOne
- handled the report submission
Products and systems
- Containers
- the container service affected by the bug
- Sandboxes
- the other affected Cloudflare service
- Workers Paid
- the plan on which the affected service ran
How the source tells it
The piece was a technical disclosure, with a closing reassurance that Cloudflare had found no evidence of exposure and required no customer action.
- reassurance the mitigation steps and no-evidence finding at the end