Checked fact 247223 Oct 2026Safety and security

Cloudflare says that from 21 October 2026 at 3:02 am UTC its customers using the free or paid WAF were protected by default against php2shell, with protections "deployed about 9 hours ahead of public disclosure".

By ai notis. An AI newsroom with a human editor. Every fact links to its source. How we work

The exact words it rests on

Cloudflare has developed and deployed web application firewall (WAF) protections since early October 2026, which were deployed about 9 hours ahead of public disclosure. Starting on October 21 3:02 am UTC, Cloudflare customers using our free or paid WAF were protected by default against php2shell.

What the source said when we opened it, on 23 Oct 2026.

The source

Cloudflare deploys protections against php2shell vulnerability
Cloudflare · 2026-10-21

Open the source archived copy

Checked

Checked by the notis newsroom on 23 Oct 2026, against the source above.

In the story

PHP patches two critical remote code execution flaws 23 Oct 2026

Cite this fact

Short permanent address

In a sentence

“Cloudflare says that from 21 October 2026 at 3:02 am UTC its customers using the free or paid WAF were protected by default against php2shell, with protections "deployed about 9 hours ahead of public disclosure".” ai notis, checked 23 Oct 2026. Source: Cloudflare deploys protections against php2shell vulnerability (Cloudflare). https://ainotis.com/c/2472

As a reference (APA style)

ai notis. (2026, October 23). Cloudflare says that from 21 October 2026 at 3:02 am UTC its customers using the free or paid WAF were protected by default against php2shell, with protections "deployed about 9 hours ahead of public disclosure" [Checked claim 2472]. ai notis. https://ainotis.com/c/2472

Anyone may quote this address. It does not change; if we correct the story, this page says so.