# Cloudflare Adds phpAfterShell Protection to WAF for Free and Paid Plans

> Cloudflare updated its WAF rule to block phpAfterShell attacks for every plan, including Free, and added three logging rules for PHP-FPM and SOAP flaws.

- Published: 2026-11-20T20:32:35+00:00
- Section: Product Launches
- Author: News Desk
- URL: https://newsforagent.com/news/2026-11-20/cloudflare-waf-phpaftershell-protection
- Source: [The Cloudflare Blog](https://blog.cloudflare.com/phpaftershell-waf-protection/)

## Key takeaways

- Cloudflare's PHP Remote Code Execution Attack rule now covers phpAfterShell (CVE-2026-126714) and defaults to Block on both managed rulesets.
- Three new rules for CVE-2026-129289, CVE-2026-15353 and CVE-2026-129506 ship in Log mode for Pro, Business and Enterprise plans.
- PHP fixed phpAfterShell and 16 other vulnerabilities on November 19, 2026, in versions 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0.

[Cloudflare](https://akta.pro/company-profiles/00006rs/cloudflare) updated its web application firewall on November 19, 2026, to block known phpAfterShell attack patterns for every customer, including those on the Free plan. The [Cloudflare Blog](https://blog.cloudflare.com/phpaftershell-waf-protection/) said the rule is part of both managed rulesets and defaults to Block.

## How the phpAfterShell Rule Works

The vulnerability, tracked as CVE-2026-126714, sits in PHP's default file-based session handler and can lead to remote code execution. Under CVSS 4.0 it scores 9.2 out of 10. The PHP project fixed it the same day in versions 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0, releases that also fix 16 other security vulnerabilities, six of them rated critical.

Cloudflare's protection comes from a PHP remote code execution rule first deployed in October 2026 for the php2shell vulnerabilities. That rule already detected part of the phpAfterShell pattern before disclosure, and Cloudflare updated its detection logic on November 19. The rule appears in the Cloudflare Free Managed Ruleset and the Cloudflare Managed Ruleset, is enabled by default, and its default action is Block. Free plan customers need take no action.

In the same release, Cloudflare added three rules to the Cloudflare Managed Ruleset for paid plans: one for a request smuggling flaw in PHP-FPM (CVE-2026-129289) and two for flaws in PHP's SOAP extension (CVE-2026-15353 and CVE-2026-129506). These are enabled by default with the Log action, because the request patterns they look for can also appear in legitimate traffic. Customers can review matches in Security Events and switch the action to Block.

Cloudflare describes the WAF as an additional layer, not a replacement for the patch. "The only complete fix is to upgrade PHP and restart every worker," the company said. As of November 19, 2026, none of the 17 vulnerabilities was listed in CISA's Known Exploited Vulnerabilities catalog, and no source reviewed by Cloudflare reports exploitation in the wild.

## Cloudflare's Network Scale Behind the WAF

According to akta.pro [company records](https://akta.pro/company-data), Cloudflare runs an anycast network in 335+ cities and blocks approximately 234 billion cyber threats daily. The same records state that Cloudflare powers approximately 1 in 5 websites on the Internet and 20% of all HTTP traffic. The company was founded in 2009 and is headquartered in San Francisco.

## Earlier Cloudflare Security Releases

Cloudflare released the original PHP remote code execution rules in an emergency release on October 21, 2026, after the php2shell vulnerabilities were disclosed, and extended them to CVE-2026-115560 on October 23. On November 13, 2026, StartupHub.ai reported that more than 50 LLM pentest orchestrator families now scan Cloudflare customers remotely, with daily tool requests up 30x since October 1. On November 8, 2026, Biometric Update reported that Cloudflare and Tools for Humanity proposed a Trusted Agent Delegation framework on November 5, 2026, to let websites distinguish legitimate AI agent activity from abuse.

## Where to Track Rule Changes

Cloudflare said customers can track rule changes in the WAF changelog and follow how the vulnerabilities develop in the dedicated Cloudflare Zero Wire briefing. The company said its analysts continue to monitor attack activity and will update the rules as new techniques and variations appear.

## Companies in this story

- [Cloudflare company profile](https://akta.pro/company-profiles/00006rs/cloudflare) · website: http://www.cloudflare.com

---
News for Agent · https://newsforagent.com/llms.txt
