Skip to content
INTERNET INFRASTRUCTURE & NETWORKS

Cloudflare Launches PHP Capture the Flag Challenge to Stress-Test WAF Protections Against Critical Vulnerabilities

Update — October 30, 2026: Cloudflare has expressed gratitude to the security research community for a robust and enthusiastic response to its ongoing PHP Capture the Flag challenge. The high volume of submissions has already provided valuable real-world data, enabling engineers to harden existing Web Application Firewall (WAF) protections associated with the php2shell threat and deploy entirely new detection mechanisms. Detailed logs of these managed-rule changes remain publicly accessible through the official Cloudflare WAF changelog.

The capture-the-flag competition remains active, with organizers encouraging security researchers to continue submitting materially distinct, reproducible bypasses through the established Cloudflare HackerOne program. Further updates and feedback will be shared as the challenge progresses.

The initiative follows a turbulent week in internet security history, marked by two severe cryptographic and runtime crises. First, security teams confronted the compromise of eight eMudhra intermediate certificates, an event that introduced the dangerous possibility of forged certificates capable of impersonating legitimate servers across the web. Shortly thereafter, the internet security landscape was rattled by php2shell, a collection of severe vulnerabilities discovered within PHP, the fundamental programming language runtime that powers a massive portion of modern web infrastructure.

As these events unfolded simultaneously, engineering and security teams at Cloudflare worked around the clock to protect customers and fortify the broader internet ecosystem. The company shipped urgent client updates alongside multiple critical mitigations, rapidly updated its web application firewall with newly developed rules designed to block attackers from exploiting the PHP vulnerabilities, and introduced a cutting-edge feature known as full transaction detection. True to the company’s standard operating principles in crisis situations, these advanced defense capabilities were made universally available across all service tiers, including free plans.

Put Our WAF to the Test

Safeguarding complex digital systems against sophisticated, rapidly evolving vulnerabilities is inherently an ongoing, iterative process rather than a one-time configuration event. The widespread adoption of artificial intelligence tools by malicious actors has fundamentally transformed the threat landscape, allowing attackers to discover new exploit vectors and deploy payloads with unprecedented speed and efficiency. Consequently, gathering empirical, real-world data to test underlying security assumptions and continuously strengthen perimeter defenses has become more essential than ever before.

To achieve this, Cloudflare launched the Cloudflare PHP Capture the Flag challenge, hosted directly through its established Bug Bounty program on HackerOne. By placing a deliberately vulnerable PHP installation safely behind its WAF, the company formally invited security researchers on the platform to attempt to bypass the deployed protective measures and successfully capture a hidden digital flag.

How This Capture the Flag Works

Designed with operational simplicity in mind, the challenge focuses squarely on CVE-2026-109618 and CVE-2026-109619, the two critical PHP vulnerabilities collectively referred to as php2shell. The target environment consists of a stock installation of PHP 8.5.11 equipped with standard PHP extensions, running alongside Apache 2 via mod_php and an empty index.php file hosted within a secure Cloudflare Container. Default WAF protection rules specifically targeting these vulnerabilities are enabled directly in front of the container, while a sensitive file named /flag rests safely inside the isolated sandbox.

To ensure a level playing field and prevent persistent tampering, the underlying sandbox environment—including the contents of the flag file itself—is automatically reset every few minutes. Security researchers willing to accept the challenge are tasked with bypassing the perimeter WAF protections, successfully exploiting the isolated PHP sandbox, and recovering the contents of the /flag file. Participants are permitted to utilize their own customized research tools, with environment details, technical scope, and an integrated flag verification form available directly on the dedicated challenge portal.

Introducing the Cloudflare PHP Capture the Flag challenge

Challenge Requirements

Because the initiative operates as a limited-time event managed through Cloudflare’s Bug Bounty program on HackerOne, all participant actions are strictly governed by standard HackerOne community terms and the specific rules of the Cloudflare bug bounty program. Researchers who manage to identify and execute an eligible security bypass must meticulously adhere to these established requirements in order to qualify for a bounty award.

Platform administrators noted that simple user interface verification does not constitute a formal HackerOne report or establish reporting priority. Certain actions are explicitly excluded from eligibility, including arbitrary file disclosure achieved without remote code execution, remote code execution performed without successful flag recovery and UI verification, local-only exploits that bypass the perimeter WAF, mere rediscovery of the already known PHP vulnerabilities, or observations of minor WAF detection differences and partial exploit chains that fail to achieve the primary objective.

Furthermore, qualifying for an award requires a materially distinct firewall bypass method, even when targeting the same underlying PHP Common Vulnerabilities and Exposures identifier. Reports that rely on the exact same firewall-bypass mechanism are automatically classified as duplicates, regardless of any superficial differences in the accompanying PHP exploit, delivered payload, remote code execution technique, or flag-recovery method. The generation of new flags, sandbox resets, attempt identifiers, cosmetic modifications, or equivalent payload encodings do not qualify a submission as unique. Equivalent submissions are treated as duplicates even if they have not yet been officially patched, meaning only the first complete, reproducible HackerOne report is considered for an award. Cloudflare retains final decision-making authority regarding duplicate classifications and reward distribution.

To assist security analysts in reviewing incoming submissions, Cloudflare records attempted request metadata and incoming payloads. Participants are strictly advised to utilize test data only and to refrain from transmitting sensitive credentials, personal information, or any other data they would not wish to preserve in a permanent security research archive. Researchers are encouraged to review Cloudflare’s privacy policy before initiating any active testing.

Active testing is strictly authorized solely against the challenge hostname’s WAF-protected endpoints utilizing the POST method, specifically targeting paths under /php/*. All other Cloudflare services, direct unauthorized access attempts against the underlying physical or virtual infrastructure, the upstream PHP open-source project, and third-party systems remain completely out of scope. Participants are prohibited from engaging in denial-of-service attacks, high-volume automated scanning, maintaining persistence within the environment, social engineering, or targeting other human participants. If rate limiting results in HTTP 429 or 503 status codes, researchers are expected to immediately back off.

In the event of any perceived conflict between the statements published in corporate blog updates and the governing Bounty Terms on HackerOne, the official Bounty Terms shall prevail. Cloudflare maintains the absolute right to suspend, modify, or terminate the challenge at any time. Once the competition listing is officially removed from HackerOne, the challenge is considered formally terminated, and participants should consult the Cloudflare HackerOne portal for the most accurate, up-to-date information regarding its operational status.

Not a Substitute for Patching

While advanced web application firewalls provide a critical layer of defense by intercepting malicious traffic at the edge, security leadership emphasizes that perimeter protection is never a permanent replacement for properly patching vulnerable software at the origin. Response blocking mechanisms can successfully prevent exposed data from reaching an unauthorized attacker, but they cannot reverse or undo malicious actions that have already been executed successfully on an unpatched origin server. Organizations running PHP environments are strongly urged to monitor the latest PHP security advisories and apply all relevant software updates promptly.

The security events of the past week served as a stark reminder that building a safer, more resilient internet relies heavily on the collaborative, urgent efforts of independent researchers, core software maintainers, and security teams across the technology industry working together under pressure. Company representatives expressed hope that the newly launched capture-the-flag challenge provides the global security community with an engaging and productive avenue to test defenses and contribute to the ongoing hardening of the web.