Checks
A name on the page is not a finished check
One row per name. Leave the result cell empty until you have an action you could fail.
blog.cloudflare.com published this account (2026-09-24): Cloudflare said a Workers Paid customer could recover residual disk blocks from other customers' containers because dm-thin pools used skip_block_zeroing. Issue reported 2026-09-04; fleet fix completed 2026-09-07; snapshot cleanup completed 2026-09-19. No CVE in the post. Cloudflare reports no evidence of malicious exploitation and no customer action required.
This guide uses that public page as the example. This site did not run the test, close the deal, or measure the product.
Write only what the page says
The page's claim is: Cloudflare said a Workers Paid customer could recover residual disk blocks from other customers' containers because dm-thin pools used skip_block_zeroing. Issue reported 2026-09-04; fleet fix completed 2026-09-07; snapshot cleanup completed 2026-09-19. No CVE in the post. Cloudflare reports no evidence of malicious exploitation and no customer action required.
Put the URL under that sentence. If a later recap adds a number or a date, keep the original page as the record.
One row per name. Leave the result cell empty until you have an action you could fail.
Do the site's check on this one page. Fill a line only when the page supports it. Where the page is silent, write Not stated.
A finished note names the page, the date, and the limit of the claim. It does not borrow a result from a different story.
Stop at the untested line
Anything you did not open, install, or count stays untested. Leave that line visible.
Source page: Cloudflare discloses Containers/Sandboxes cross-tenant residual disk exposure.
Sources: Cloudflare discloses Containers/Sandboxes cross-tenant residual disk exposure