Cloudflare incident: skipped block zeroing leaked tenant data across 18 of 24 containers
arpit_bhayani · x · 2026-09-28
Arpit Bhayani breaks down a Cloudflare incident around zeroing storage in a multi-tenant system.
- The shared pool reused deleted blocks without zeroing. Since thin volumes allocate on first write, a 4 KiB write grabs a recycled 64 KiB block — the remaining 60 KiB holds the previous tenant's data.
- Residual data was found on 18 of 24 container placements and 20 of 22 nodes: other customers' directory listings, database pages, complete SQLite databases, Chromium profiles, .env and credential files.
- Skipping zeroing is usually a performance trade-off (extra I/O per reclaimed block).
- Advice: if you build on shared block storage, thin provisioning, or pooled volumes, check what happens to a block between owners. The issue is now fixed.
Related event: Cloudflare Patches Cross-Tenant Leak from Unwiped Storage Blocks(2 posts)→
More from Infra
- 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
- Sarvam AI Launches Token Factory: India-Hosted Inference for Open Models — itsOmSarraf_ · 2026-11-16
- BIS Issues Interim Final Rule Addressing Remote Access to Advanced AI Chips — apples_jimmy · 2026-11-16
- Jailbroken PS4 runs a 9B open-source model at up to 43 tok/s by talking directly to its 2013-era GPU — AIFlow_ML · 2026-11-16
- Mobile AI Factory: agents auto-build on-device SLMs with 19x less GPU time — pmttyji · 2026-11-16