Cloudflare WAF updates rules to defend against phpAfterShell
Understand this story
On November 19, Cloudflare updated its WAF rule detection logic to cover the phpAfterShell (CVE-2026-126714) attack pattern and added the CVE number to the rule description. Cloudflare says its WAF can block known phpAfterShell attack patterns, that Free plan users are covered as well, and that no action is required. The rules are enabled by default with a Log action rather than blocking outright, because the request patterns they match can also appear in normal traffic, and blocking by default could cause false positives. Cloudflare also stressed that the WAF is only an extra layer of defense and cannot replace installing patches.
AI overview based on source reports · Updated 56 min ago
Coverage timeline
Follow the coverage to explore different perspectives.
- Cloudflare BlogHow Cloudflare WAF helps protect against phpAfterShell and other critical PHP flaws
Cloudflare says its WAF blocks known phpAfterShell (CVE-2026-126714) attack patterns on all plans, including Free, via an updated PHP remote code execution rule, and adds three new Log-action rules for paid plans covering a PHP-FPM request smuggling flaw and two SOAP extension flaws. PHP fixed phpAfterShell and 16 other vulnerabilities, six also critical, on November 19, 2026 in versions 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0. Cloudflare states the WAF is an additional layer of defense, not a replacement for patching, and that no exploitation in the wild had been reported as of November 19, 2026.
Activity for this story
Not enough continuous observations to show a trend yet.