Update — October 30, 2026: Cloudflare has expressed gratitude to the security research community for a strong and active response to its ongoing PHP Capture the Flag (CTF) challenge. Submissions received from participating researchers have already played a crucial role in helping engineers harden existing php2shell Web Application Firewall (WAF) protections and deploy newly developed detection mechanisms. Details regarding these managed-rule changes have been made publicly available through the official Cloudflare WAF changelog. Meanwhile, the CTF environment remains active and open to the public. Security researchers are actively encouraged to continue submitting materially distinct, reproducible bypasses through Cloudflare’s HackerOne program, with further updates and community feedback to be shared as the challenge progresses.
The preceding week will undoubtedly be remembered in internet security history books as a period of intense turbulence and rapid defensive mobilization. The crisis began unfolding when eight eMudhra intermediate certificates were compromised, introducing the alarming possibility of forged digital certificates that could potentially be leveraged by malicious actors to impersonate legitimate servers across the global web ecosystem. Almost immediately following that disclosure, the security community was struck by "php2shell," a series of highly serious vulnerabilities discovered within PHP, the foundational runtime language that quietly powers a massive portion of the modern web infrastructure.
As these critical events unfolded simultaneously, security engineering teams at Cloudflare worked around the clock to safeguard their extensive customer base and contribute to the broader protection of the internet at large. The company swiftly shipped client updates alongside multiple targeted mitigations to address the certificate compromise. Simultaneously, engineers updated their web application firewall architecture with specialized new rules specifically designed to block attackers from exploiting the newly uncovered PHP vulnerabilities. In tandem with these updates, Cloudflare introduced an innovative defense capability known as full transaction detection, designed to inspect complete request and response lifecycles for malicious patterns. True to the company’s established operational model, these advanced new protective capabilities were made universally available across all service tiers, including completely free accounts, ensuring that organizations of all sizes could benefit from immediate remediation.
Put Our WAF to the Test
Defending complex distributed systems against sophisticated and rapidly evolving vulnerabilities is inherently an ongoing operational process rather than a static, one-time event. The widespread and increasingly accessible adoption of artificial intelligence by malicious actors allows attackers to discover novel attack vectors and weaponize exploits with unprecedented speed and operational efficiency. Consequently, collecting authentic, real-world data to test underlying security assumptions and continuously strengthen perimeter defenses has become an absolute necessity for modern infrastructure providers.
To address this pressing challenge head-on, 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 directly behind their production-grade WAF, the company invited skilled security researchers on the HackerOne platform to attempt to bypass the implemented protective measures and successfully capture a designated digital flag. This crowdsourced approach aims to stress-test defensive assumptions under realistic conditions and surface subtle edge cases before malicious actors can exploit them in the wild.
How This Capture the Flag Works
Cloudflare designed the challenge structure to remain straightforward while maintaining rigorous testing standards. The entire exercise focuses squarely on CVE-2026-109618 and CVE-2026-109619, the two critical PHP vulnerabilities that collectively underpin the php2shell threat vector. The target environment runs a stock installation of PHP 8.5.11 equipped with standard PHP extensions, running alongside Apache 2 via mod_php, and featuring an empty index.php file hosted within a secure Cloudflare Container. The default WAF protection rules specifically tailored for these PHP vulnerabilities are enabled directly in front of this sandbox environment. Tucked safely inside the sandbox is a specific target file designated as /flag.
To ensure the integrity of the challenge and prevent persistent unauthorized modifications, the sandbox environment is automatically reset every few minutes, which includes regenerating and replacing the contents of the flag file.
The core mission presented to participating researchers is concise: bypass the active WAF protections, successfully exploit the underlying PHP sandbox environment, and recover the exact contents of the /flag file. Researchers are permitted to utilize their own custom research tools and methodologies. Comprehensive details regarding the target environment, operational scope, and a dedicated flag verification form have been made available directly on the official challenge web page.

Challenge Requirements
This limited-time security challenge is governed strictly through Cloudflare’s Bug Bounty program hosted on HackerOne. All aspects of participation remain subject to standard HackerOne community terms and Cloudflare’s specific HackerOne program rules, collectively referred to as the bounty terms. Researchers who discover an eligible and reproducible bypass must strictly adhere to established reporting requirements in order to qualify for any bounty awards.
The automated user interface verification feature is strictly a convenience tool for participants and does not automatically submit a formal HackerOne report or establish priority for reporting. Several types of submissions are explicitly deemed ineligible for bounties, including arbitrary file disclosure without remote code execution (RCE), RCE without successful flag recovery and corresponding UI verification, local-only exploits that do not involve the WAF perimeter, simple rediscovery of the already known PHP vulnerabilities, and minor WAF detection differences or partial exploit chains that fail to achieve the full objective.
A critical rule governing the competition is that awards require a materially distinct firewall bypass method, even when targeting the same underlying PHP CVE. Reports that rely on the exact same firewall-bypass mechanism will be classified as duplicates, regardless of any variations in the specific PHP exploit used, the payload structure, the remote code execution technique, or the method of flag recovery. Introducing new flags, environment resets, unique attempt identifiers, cosmetic modifications, or equivalent payload encodings do not qualify a submission as unique. Equivalent submissions will be treated as duplicates even if they have not yet been formally patched; only the first complete, fully reproducible HackerOne report submitted will be considered for an award. Cloudflare retains final authority on all duplicate determinations and reward decisions.
Because Cloudflare records attempt metadata and request payloads to assist engineering teams in analyzing security reports, participants are strictly advised to use test data only. Researchers must refrain from sending sensitive credentials, personal identifiable information, or any other data they would not wish to be included in an official security research record. All participants are encouraged to review Cloudflare’s privacy notice prior to initiating any testing activities.
Security testing is explicitly authorized solely against the designated challenge hostname’s WAF-protected endpoints located at /php/* using the HTTP POST method exclusively. Other Cloudflare services, direct access attempts against the underlying cloud infrastructure, the upstream PHP open-source project, and third-party systems remain entirely out of scope. Participants are expressly prohibited from engaging in denial of service attacks, high-volume automated scanning, establishing persistent access, utilizing social engineering tactics, or targeting other human participants. If automated rate-limiting results in a 429 or 503 HTTP status code response, researchers must immediately back off.
In the event of any interpretive conflict between this public announcement and the official bounty terms, the bounty terms shall permanently prevail. Furthermore, Cloudflare retains the absolute right to suspend, modify, or terminate the challenge at any time at its sole discretion. Once the competition is officially removed from the HackerOne platform, it is considered formally terminated, and participants should consult the official Cloudflare HackerOne page for the most up-to-date status regarding whether the challenge remains open.
Not a Substitute for Patching
While advanced web application firewalls provide critical defensive layers and rapid response capabilities, Cloudflare emphasizes that a WAF 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 magically undo malicious actions that have already been executed on vulnerable origin servers. Organizations running PHP in production environments are strongly urged to closely 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 helping to build a safer, more resilient internet frequently requires coordinated efforts from many different groups—including independent security researchers, software maintainers, and corporate engineering teams across the entire technology industry—working together under intense pressure to solve urgent problems.
Cloudflare expressed hope that this interactive CTF challenge provides security professionals with a useful, engaging mechanism to participate in that ongoing defense. Researchers interested in testing their skills can visit the challenge portal to examine the environment, as the flag remains hidden behind the defenses, waiting to see if the security community can successfully retrieve it.