Cloudflare’s latest WAF emergency release modifies the PHP remote‑code‑execution rule for better detection and adds a handful of new rules targeting recent PHP and Ruby vulnerabilities. The new PHP rules are deployed in log‑only mode by default, while the Ruby rules are set to block. Teams that rely on Cloudflare’s Free or Managed rulesets need to verify that the new actions align with their security posture.
Rule changes overview
- PHP remote‑code‑execution rule (CVE‑2026‑109618, CVE‑2026‑109619, CVE‑2026‑115560, CVE‑2026‑126714) now has an updated detection signature and is set to
Blockin both Free and Managed rulesets. - Two Ruby overflow detections – a heap overflow (CVE‑2026‑13282) and an integer overflow (GHSA‑87fm‑7w84‑j2px) – are added to both Free and Managed rulesets with a
Blockaction. - Three new PHP‑related detections are introduced in the Managed ruleset only: a PHP‑FPM issue (CVE‑2026‑129289), a PHP SOAP flaw (CVE‑2026‑15353), and a generic PHP rule. All three are set to
Logby default.
Operational impact
Because the new PHP rules start in log mode, they will not interrupt legitimate traffic until an operator reviews the logged events and decides whether to promote the rule to Block. This approach reduces the risk of false positives but adds a monitoring step. Engineers should add the rule IDs (e.g., 8660e37e86444f9f9267ba22e9855f05 for the PHP‑FPM rule) to their WAF dashboards and set up alerts for any logged matches.
For the Ruby rules, the immediate block action means that any request matching the overflow signatures will be denied outright. Teams must verify that legitimate Ruby applications do not generate traffic patterns that could be mistaken for the overflow signatures, otherwise they may need to create custom exceptions.
Security considerations
The updated PHP remote‑code‑execution rule improves detection accuracy, which can reduce the window of exposure for the listed CVEs. However, the default log mode for the new PHP rules means that exploitation attempts will be observed but not stopped automatically. Organizations with high‑value PHP workloads should evaluate the risk tolerance and consider moving those rules to Block after confirming low false‑positive rates.
Ruby applications now have explicit protection against two newly disclosed overflow vulnerabilities. Since the action is Block, any attempted exploitation will be halted at the edge, providing immediate mitigation without additional configuration.
Related CloudNinjas coverage: security.
What This Means For Practitioners
- Review the rule IDs introduced in this release and confirm they are present in your active ruleset.
- Enable logging alerts for the new PHP rules and schedule a review of logged events within the first 24‑48 hours.
- If your environment tolerates a higher false‑positive rate, consider promoting the PHP rules to
Blockafter validation. - Test Ruby applications against the new overflow signatures to ensure legitimate traffic is not unintentionally blocked.
- Update any internal WAF documentation to reflect the changed actions and the rationale for default log mode.

