Cloudflare disclosed a vulnerability in its Containers platform on September 25, 2026, that allowed paying customers to read leftover disk data from other customers’ previous containers. The flaw violated the multi-tenant isolation controls that prevent one customer from accessing another customer’s data, though the exposed data came from disk space that earlier containers had used and released rather than from live workloads.
How the Disk Data Leakage Occurred in Cloudflare’s Multi-Tenant Environment
The vulnerability exploited the way Cloudflare Containers allocated disk space to new customer workloads. When a customer’s container ended and released its storage, the disk blocks it had occupied returned to the shared pool available for future containers. If Cloudflare did not properly wipe or zero those blocks before assigning them to a different customer’s container, the new tenant could read residual data written by the previous tenant.
This type of data leakage differs from an active breach targeting live systems. The attacker could not choose whose data they would access—they simply received whatever happened to remain on the disk space assigned to their new container. The randomness limits the attack’s usefulness for targeted espionage but still represents a fundamental failure of tenant isolation, one of the core security promises of any multi-tenant cloud platform.
What Customer Data Remained Vulnerable to Cross-Tenant Access
Cloudflare confirmed the flaw allowed customers to read data from previously used disk space but did not specify what types of customer information were exposed. Container environments typically store application code, configuration files, temporary data written during container execution, and any secrets or credentials the containerized application used. The severity depends on what customers stored in containers and whether sensitive data was written to disk rather than kept in memory or encrypted at rest.
The disclosure did not address how long the vulnerability existed, how many customers were potentially affected, or whether Cloudflare detected any instances of customers actually exploiting the flaw to access others’ data. The lack of targeting capability—attackers could not select which prior customer’s data they accessed—may have reduced the likelihood that the vulnerability was actively exploited for espionage, but opportunistic data harvesting across random disk allocations could still yield credentials, API keys, or proprietary application logic.
Cloudflare and Researchers Disclose Flaw After Fix Deployment
Cloudflare fixed the vulnerability and disclosed it publicly on September 25, 2026, alongside security researchers who presumably discovered or reported the issue. The joint disclosure suggests coordinated vulnerability disclosure practices, with researchers giving Cloudflare time to deploy a fix before making the flaw public.
The fix likely involves properly wiping or zeroing disk blocks before reallocating them to new containers, a standard practice in multi-tenant environments designed to prevent exactly this type of data leakage. That the vulnerability existed at all indicates Cloudflare’s container provisioning process either skipped this sanitization step or failed to execute it correctly across all disk allocation paths.
Multi-Tenant Isolation Failures and Cloud Customer Data Protection Expectations
Multi-tenant cloud platforms build their security models on isolation guarantees: one customer’s workload should never see another customer’s data, even when both run on shared infrastructure. Disk space allocation is a well-understood isolation boundary, and wiping residual data before reuse is a decades-old defensive practice in shared computing environments.
The Cloudflare Containers flaw demonstrates that even mature cloud providers can fail to implement basic isolation controls correctly. For customers evaluating cloud platforms, the incident highlights the importance of assuming isolation failures are possible and implementing defense-in-depth measures—encrypting data at rest, minimizing what containerized applications write to disk, and treating any cloud storage as potentially observable by other tenants.
The disclosure also raises questions about how many other cloud container platforms have similar disk-sanitization gaps. Cloudflare fixed this instance, but the same class of vulnerability could affect any multi-tenant system that reallocates storage without verifying prior data has been removed. The public disclosure may prompt other cloud providers to audit their own container provisioning processes for comparable weaknesses.
