search
Cloudflare Containers
Trends
- 1Cloudflare Patches Critical Flaw Exposing Container Data●Cloudflare Fixes Critical Flaw Exposing Customers’ Container Data
Cloudflare has fixed a critical vulnerability that could have exposed customers' container data. The flaw, disclosed and patched by the company, raised concerns about isolation between customer workloads in its container platform. Security professionals are closely watching the disclosure for details on exploitation and impact, as the incident underscores ongoing risks in shared cloud infrastructure.
- 2Cloudflare patches cross-tenant flaw in Containers product●Cloudflare fixes Containers cross-tenant flaw exposing customer data
Cloudflare has fixed a cross-tenant vulnerability in its Containers service that could have exposed customer data between tenants. The flaw, reported by BleepingComputer, was patched after discovery, and the company says the issue affected isolation boundaries in the product. Security researchers and customers are watching the disclosure closely, as cross-tenant bugs in major cloud providers raise concerns about data separation and trust in shared infrastructure.
- 3Cloudflare Containers flaw exposed cross-tenant data fragments●Discover how a Cloudflare Containers data flaw exposed cross-tenant fragments. Learn about the skip_block_zeroing thin p
A security write-up describes a flaw in Cloudflare Containers where data fragments from one customer could potentially be exposed to another. The issue is linked to the skip_block_zeroing behaviour of thin provisioning, meaning storage blocks were not wiped before reuse. Discussion is circulating among cybersecurity communities, raising concerns about isolation guarantees in shared cloud infrastructure.
- 4Cloudflare fixes cross-tenant data exposure in Containers sandboxes●🤖 Cloudflare Containers/Sandboxes cross-tenant data exposure: dm-thin storage pools ran with skip_block_zeroing, so a Wo
A cross-tenant data exposure flaw in Cloudflare's Containers and Sandboxes has been disclosed and fixed. The issue stemmed from dm-thin storage pools running with skip_block_zeroing enabled, meaning newly written 4 KiB pages into unmapped 64 KiB blocks could leave residual data on raw devices. A Workers Paid tenant could reportedly read up to 60 KiB of data left behind by a previous tenant from /dev/vdc. Cloudflare has patched the issue, and security communities are discussing the implications of shared-storage isolation failures in multi-tenant cloud platforms.