---
type: "post"
id: "cloudflare-updates-php-vulnerability-waf-detections-after-ctf-56f7e5"
slug: "cloudflare-updates-php-vulnerability-waf-detections-after-ctf-56f7e5"
title: "Cloudflare updates PHP vulnerability WAF detections after CTF submissions"
description: "Cloudflare says it updated Web Application Firewall detection expressions for three PHP out-of-memory vulnerabilities after reports from researchers in its PHP Capture the Flag challenge."
retrieval_nugget: "Cloudflare says it updated Web Application Firewall detection expressions for three PHP out-of-memory vulnerabilities after reports from researchers in its PHP Capture the Flag challenge. The changes refine existing blocking rules across several rulesets, extending New Runtime’s earlier coverage of Cloudflare’s PHP protections."
published_at: "2026-11-16"
updated_at: "2026-11-16"
record_date: "2026-11-16"
date_kind: "published_at"
topics: ["security"]
entities: ["Cloudflare","Cloudflare WAF","PHP Capture the Flag"]
related_patterns: []
novelty_label: "new_fact"
what_changed: "Cloudflare refined WAF detection rules for three PHP out-of-memory vulnerabilities based on researchers’ submissions to its PHP Capture the Flag challenge."
prior_refs: []
source_url: "https://developers.cloudflare.com/changelog/post/2026-10-30-waf-release"
source_urls: ["https://developers.cloudflare.com/changelog/post/2026-10-30-waf-release"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:cloudflare-updates-php-vulnerability-waf-detections-after-ctf-56f7e5"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/cloudflare-updates-php-vulnerability-waf-detections-after-ctf-56f7e5/","markdown":"https://newruntime.com/posts/cloudflare-updates-php-vulnerability-waf-detections-after-ctf-56f7e5.md","json":"https://newruntime.com/posts/cloudflare-updates-php-vulnerability-waf-detections-after-ctf-56f7e5.json"}
markdown_url: "https://newruntime.com/posts/cloudflare-updates-php-vulnerability-waf-detections-after-ctf-56f7e5.md"
---

# Cloudflare updates PHP vulnerability WAF detections after CTF submissions

## Retrieval answer

Cloudflare says it updated Web Application Firewall detection expressions for three PHP out-of-memory vulnerabilities after reports from researchers in its PHP Capture the Flag challenge. The changes refine existing blocking rules across several rulesets, extending New Runtime’s earlier coverage of Cloudflare’s PHP protections.

## Summary
Cloudflare says it updated Web Application Firewall detection expressions for three PHP out-of-memory vulnerabilities after reports from researchers in its PHP Capture the Flag challenge. The changes refine existing blocking rules across several rulesets, extending New Runtime’s earlier coverage of Cloudflare’s PHP protections.

## What happened
Cloudflare’s October 30, 2026 WAF changelog says the release updates underlying rule expressions for PHP out-of-memory vulnerabilities CVE-2026-109618, CVE-2026-109619 and CVE-2026-115560. The company describes the work as iterative changes based on reports from security researchers participating in its PHP Capture the Flag challenge.

The changelog lists updated detection for “PHP Remote Code Execution Attack” rules associated with CVE-2026-109618 and CVE-2026-109619. In the Cloudflare Free Ruleset, rules #3 and #4 have their detection updated, with both the previous and new action listed as Block. The Cloudflare Managed Ruleset has corresponding updates to rules #3 and #4, also retaining Block as the action. The rule identifiers shown for those entries are 82dab691 and 24b1a4c6 in the Free Ruleset, and 545d163c and 212afcc9 in the Managed Ruleset.

A separate entry records an updated detection for “Default block for High confidence Signatures” in the Cloudflare Response Ruleset. That entry’s rule identifier is 48d2242a, and its action remains Block. Across the entries Cloudflare identifies, the release is an improvement to detection rather than a change in what the rules do after a match: every recorded action remains blocking.

The release names three CVEs in its introduction, but the four explicitly named remote-code-execution rule entries cite CVE-2026-109618 and CVE-2026-109619. Cloudflare does not assign CVE-2026-115560 to an individual table entry in the changelog. It also does not announce a new ruleset, a new WAF action, a pricing change, or a revised access tier. The named protections span the Free Ruleset, Managed Ruleset and Response Ruleset already operated by Cloudflare.

Cloudflare does not publish the revised expressions, request examples, deployment instructions, or customer configuration steps in this release note. Nor does it say whether customers must take an action for the refinements to apply. The company’s stated change is narrower: detections within existing blocking controls have been updated in response to CTF researcher reports. That makes this a security-maintenance release with a visible record of which rules changed, rather than a newly announced product capability.

## What the archive adds
New Runtime covered Cloudflare’s deployment of default WAF protections for PHP vulnerabilities it called php2shell on [October 22, 2026](https://newruntime.com/posts/cloudflare-deploys-protections-against-php2shell-vulnerability-9a828a/). This is a new fact on that known story: Cloudflare now documents iterative detection updates informed by CTF researcher reports, while the earlier note covered the initial protections.

## Trend signal
This update is adjacent to [agent security moving to runtime boundaries](https://newruntime.com/patterns/agent-security-moves-to-runtime-boundaries/), but does not materially demonstrate the pattern: Cloudflare describes WAF rule updates for PHP vulnerabilities, not controls over an agent’s execution or authority. This does not yet fit a pattern New Runtime tracks.

## Why it matters
For teams running PHP services behind Cloudflare, the changelog is a reminder that a defensive control can improve without changing its visible action. The relevant rules still block, while the detection expressions are refined. That distinction matters in security operations: an unchanged “Block” label is not evidence that the logic determining a match has remained fixed.

The operational consequence is modest but real. Teams that use Cloudflare WAF as part of a broader exposure-management process should treat vendor-managed detections as a maintained layer, not as a one-time setting recorded at rollout. Change review should distinguish between policy actions, such as Block or Log, and the signatures or expressions that feed those actions. This release documents movement in the latter category.

Cloudflare also identifies a feedback route: researcher reports in a CTF challenge informed iterative rule changes. The company does not describe a reusable process in detail, but the release illustrates why vulnerability controls need continual testing and revision. Teams should verify which Cloudflare rulesets they use, retain their own application patching and monitoring processes, and consult Cloudflare documentation before altering production controls.

## Limits and uncertainty
Cloudflare does not disclose the revised expressions, the specific researcher reports behind them, or the request patterns that changed. The changelog provides no before-and-after detection results, false-positive measurements, exploitation data, or independent validation of the updates. It does not state the rollout timing or whether application traffic will encounter any changed behavior beyond the rules’ continuing Block action.

The company also does not explain the relationship between all three CVEs named in the introduction and each listed rule. The named remote-code-execution entries cite two CVEs, while the release introduction includes a third. Because the underlying expressions are unpublished, it is not possible to assess coverage quality, bypass resistance, or the risk of new false positives from this announcement alone.

## Reader takeaway
Cloudflare’s release is a focused refinement of existing PHP vulnerability detections, not a new blocking action. For teams using these rules, the meaningful change is in what the WAF recognizes. The changelog confirms that detection expressions changed, but it does not establish how much protection improved or how customer traffic will be affected.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Security](https://newruntime.com/topics/security.md): Explore the security topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)
