Cloudflare WAF blocks phpAfterShell and six other critical PHP flaws

·2026.11.21 05:00

Key point

The vulnerability, fixed in PHP 8.2.36 through 8.6.0, allows remote code execution via interrupted session writes, with no known exploitation in the wild as of November 19, 2026.

Details

  • Cloudflare WAF blocks known phpAfterShell (CVE-2026-126714) attack patterns for all customers, including the Free plan, using a rule updated on November 19, 2026.
  • The vulnerability, rated CVSS 9.2, was fixed in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, and 8.6.0, which also patch six other critical flaws.
  • New WAF rules for PHP-FPM (CVE-2026-129289) and SOAP extension flaws (CVE-2026-15353, CVE-2026-129506) are enabled in Log mode for paid plans to avoid disrupting legitimate traffic.
  • No exploitation has been reported in the wild or listed in CISA's Known Exploited Vulnerabilities catalog as of November 19, 2026.

Vulnerability Mechanics

  • phpAfterShell exploits an interrupted write in PHP's default file-based session handler, causing deserialization of mixed old and new session data.
  • Exploitation requires an attacker to control session data via session upload progress or large user-controlled strings, plus a deserialization gadget chain or a second undisclosed memory-corruption bug.
  • The other critical flaws include a request smuggling issue in PHP-FPM and use-after-free errors in timezone caches and fatal error backtraces, each requiring specific server configurations.

Mitigation and Scope

  • WAF protection is an additional layer, not a replacement for patching, as it cannot see internal traffic, server-state flaws, or session data from non-HTTP sources.
  • Affected versions are PHP 8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13, and 8.6.0 release candidates.
  • Interim mitigations include disabling session.upload_progress.enabled, turning off FastCGI connection reuse, and setting fatal_error_backtraces=0 on PHP 8.5.

This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.

Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.