The Cloudflare Container Disk Data Leak: A Shared Infrastructure Vulnerability Explained

Cloudflare Containers are a service that runs customer code in isolated environments on Cloudflare's edge network. The flaw allowed a paying customer to read undeleted data left on disk by other customers' containers after they finished running and released the resources. This was not a live data breach; the attacker could not intercept active workloads or choose whose data they recovered. They could only stumble upon fragments of what previous containers had left behind on the same server.

Data residue on disk is a known risk in multi-tenant cloud systems. When a container stops, the operating system does not automatically wipe every byte of the disk space it used. Other containers on the same physical hardware could potentially read that space if they had the right access level, which is exactly what happened here.

Cloudflare runs millions of containers across its infrastructure to handle customer workloads cheaply and at scale. Keeping these workloads separate is not just a feature; it is a security boundary. If one customer can read another customer's disk fragments, the fundamental promise of isolation fails, even if the breach is partial and non-selective.

The vulnerability revealed that Cloudflare's disk cleanup between container runs had a gap. Sensitive data like API keys, database credentials, or customer records could have persisted on disk longer than intended. A customer with legitimate access to the Containers service could exploit this to recover information they had no right to see.

This is especially concerning for companies using Cloudflare Containers to process payments, handle authentication, or work with protected data. Even though an attacker could not choose their target, they could keep running containers until they found something valuable in the residual data.

Cloudflare and the researchers who discovered the flaw coordinated a responsible disclosure, meaning the vulnerability was reported privately and fixed before public details were released. The fix likely involved one or more of these approaches:

1. Overwriting disk space with zeros or random data when containers release resources
2. Encrypting disk data so that residual fragments are unreadable without the proper keys
3. Partitioning disk access more strictly so containers cannot read space allocated to others
4. Adding filesystem barriers that prevent one container's process from accessing blocks owned by a different tenant

Cloudflare announced the issue on September 25, 2026, and stated that customers did not need to rotate credentials or take emergency action. The company's transparency about the nature of the flaw (targeted at historical data, not live workloads) helped reduce panic while reinforcing the importance of fixing it.

This incident reflects a broader reality about cloud platforms and shared infrastructure. Isolation is not achieved by good intentions; it requires multiple layers of technical controls. Disk space cleanup is easy to overlook in architecture reviews because it feels like a low-level operating system detail, but it is a real attack surface.

From a law-enforcement and security research perspective, this kind of data residue has been studied for decades. Decommissioned hard drives and repurposed cloud storage often contain recoverable traces of previous users' data. Cloudflare's mistake was not unusual; it was a failure to apply a well-known mitigation at the implementation stage.

For users of Cloudflare Containers or any edge computing platform, this disclosure is a reminder that shared infrastructure means accepting some level of residual risk, no matter how well-designed the system is. The right response is not to assume breach; it is to assume that such gaps will eventually exist and to design your workloads accordingly.

Cloudflare did not disclose the exact technical details of the patch, which is standard practice to avoid helping attackers exploit older versions. However, the fix ensures that disk space is sanitized before containers reuse it. This is similar to how secure deletion tools work on personal computers, but applied automatically and at the platform level.

Customers using Cloudflare Containers received no breaking changes. The service continued to function the same way from an API perspective; only the underlying cleanup process was hardened. Cloudflare also likely updated its internal security testing to detect similar residue issues in other services.

This vulnerability was not a catastrophe, but it was a wake-up call about the hidden costs of edge computing and serverless platforms. Sharing physical resources across customers is how these services stay affordable, but sharing creates new security boundaries to defend. Cloudflare fixed the flaw, but the broader lesson remains: any platform promising isolation in a multi-tenant environment must actively prove it through testing, design review and, when necessary, public disclosure.

If you run workloads on any cloud platform, review your incident response plan and consider whether your threat model accounts for residual data leaks. Ask your provider what they do to sanitize resources between tenants, and request documentation of their security controls.

Source: The Hacker News