Cloudflare fixes cross-tenant flaw: unzeroed storage blocks leaked customer container data
arpit_bhayani · x · 2026-09-28
A detailed breakdown of the Cloudflare Containers/Sandboxes cross-tenant data exposure flaw.
Root cause
- The shared storage pool was configured to skip zeroing reused 64 KiB blocks when a volume was deleted
- Containers use thin volumes that allocate physical blocks on first write, so writing just 4 KiB to an unused region triggered allocation of a reused block — leaving the other 60 KiB readable with the previous tenant's data
Impact
- Workers Paid customers could read residual files from other customers' containers: directory listings, SQLite databases, Chromium profiles, .env and credential files
- Residual data was found on 18 of 24 container placements and 20 of 22 underlying nodes tested
Disclosure
Reported Sept 4 via HackerOne by Oren Yomtov (Accomplish); Cloudflare has fixed it and published a disclosure.
Related event: Cloudflare Patches Cross-Tenant Leak from Unwiped Storage Blocks(2 posts)→
More from Infra
- Training-free page-sparse decode in llama.cpp: 1.72× faster 128k decoding on an RTX 5090 — topppggg · 2026-11-16
- llama.cpp offloads CI caches and runners to Hugging Face to survive 35 PRs/day — ggerganov · 2026-11-16
- India's Sarvam launches Token Factory, hosting top open models on local infra — HarveenChadha · 2026-11-16
- ZGX Fury stress-tested: 351 tok/s on Qwen3.8-Flash-Next, offline agents and local RAG demos — Sam Witteveen · 2026-11-16
- Gemini 3.5 Flash now runs on air-gapped Google Distributed Cloud, offline up to 12 months — shashib · 2026-11-16
- Gemma.c: full Gemma 1/2/3 multimodal inference in a single C file, ~72 tok/s on CPU at INT8 — This-Purchase-3325 · 2026-11-16