Calif
Ryan Austin
Found Aug. 1 · reported Aug. 11
Joined OpenAI’s Patch the Planet program July 30, where PHP stood out as a high-impact target.
[8]
Modelsdo not reliably begin with obscure twenty-year-old exploitation primitives.[8]
PHP · Cloudflare · Oct. 20 to 22, 2026
PHP is the programming language that builds the pages of about 69 in every 100 websites whose server language is known. [23] On October 21 the PHP project shipped fixes for two flaws, nicknamed PHP2Shell, that let anyone run their own commands on a site’s server over the web, with no login. [1][6] That night Cloudflare’s chief executive posted that attempts to use them on its network had gone from thousands, in the 10 hours before the announcement, to millions. [13]
websites whose server-side language is known run PHP, by W3Techs’ count on Oct. 22, 2026. [23]
PHP’s own site: it powers everything from your blog to the most popular websites in the world.
[11]
The fix has to be installed on each server by whoever runs it; updating the website itself does not fix PHP. [6][12] On October 21 BambooHR’s HR and payroll service and Dutch government sites went offline as a precaution. [19][20]
Not yet published
Disclosure: Anthropic is the company that makes Claude, the AI that helps make this site. The PHP Foundation says it worked with Alpha-Omega to scan PHP with Anthropic’s Claude Mythos earlier this year, and thanks Alpha-Omega, OpenAI and Anthropic for giving the team access to their tools and funding some of the security work.
Anthropic is not among the finders it credits for these two flaws. [5]
What it is
Unauthenticatedmeans no login first. PHP rates both flaws 9.2 out of 10. [2][3][4]
CVE-2026-109618, RCE via OOM corruption
: out-of-memory handling can interrupt PHP while internal request data is only partially initialized. Request cleanup may then treat the invalid data as valid.
[1] The confirmed impact is unauthenticated remote code execution as the web worker account.
[3]
CVE-2026-109619, RCE via stale global state
: request-owned internal state can survive after its backing memory has been freed. A later request handled by the same worker may use that stale state before normal initialization resets it.
[1] Session upload progress can reach session handling before ordinary session initialization.
Its confirmed impact includes memory disclosure and remote code execution
. [4]
Who is at risk: all PHP installations serving web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. We consider the risk highest for mod_php, with a demonstrated exploit where an unauthenticated request can trigger the attack before any application code runs.
[1] For PHP-FPM, the advisory says no complete exploit has been shown. [3]
What can leak: Wiz says leaked memory may hold passwords, authentication tokens, API keys and certificates
from other requests or the server. [7]
The race
In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.[13]Matthew Prince, Cloudflare’s chief executive, on X, 9:25 PM ET Wednesday, Oct. 21 (01:25 UTC Thursday)
thousandsis 1,000 to 9,999); his post gives no exact counts. Times are Eastern. [12][13]
has not observed exploitation of these vulnerabilities as of the time of publication.[18] The Dutch National Cyber Security Centre said a day later,
We see attempts to exploit the vulnerabilities.(translated) [21] No source on the record confirms a successful break-in. [27]
PHP sites behind Cloudflare already have an initial set of WAF rules deployed.[14]
it remains unclear how the actor acquired exploit information prior to disclosure.It adds,
it’s unclear if any of these attempts would have succeeded in real-world systems.[17]
Who it reaches
of all websites run WordPress (39.6, by W3Techs’ count), which is built on PHP. [22][24] Wiz says it confirmed the attack against WordPress and Drupal in August. [7]
As each one announced it, or as reported.
We know this interrupts essential work, including payroll.[19] midnight ET7:51 AM to 2:01 PMmidnight
the outages were not caused by exploitation of the vulnerabilities or by a cyber breach.Japan’s National Tax Agency took its service down; the Finance Ministry and Meteorological Agency partly suspended theirs. [29]
What to do
PHP: There are no complete mitigations, updating is the only safe choice.
[1]
| If you run | Fixed in | Note |
|---|---|---|
| PHP 8.5 | 8.5.12 | |
| PHP 8.4 | 8.4.27 | |
| PHP 8.3 | 8.3.36 | |
| PHP 8.2 | 8.2.35 | End of life Dec. 31, 2026 |
| 7.4 to 8.1 | no release | PHP posted source patches; some vendors ship fixes |
| 5.4 to 7.3 | no fix | PHP: upgrade to a supported version |
CISA: systems that can’t be updated right away, or that run PHP 8.1 or earlier, should go offline until they can be patched or updated.
[18]
PHP says these reduce exposure to specific attack paths but do not make an installation safe.
[1]
For CVE-2026-109618: set memory_limit=-1 where applications can’t override it; set a low post_max_size (8M without uploads, 32M with); enforce request-size limits at the web server or proxy; do not use RLIMIT_AS or RLIMIT_DATA. [1]
For CVE-2026-109619: Set session.upload_progress.enabled=0 and restart every worker.
On PHP 8.5, also set fatal_error_backtraces=0 and restart every worker. [1]
Signs to look for: unexpectedly large or malformed PHPSESSID response cookies, unusual multipart requests (uploads) followed by memory-limit errors or repeated HTTP 500 responses, unexplained PHP worker crashes or restarts [6], and PHP worker processes launching shells or downloading tools. [18] The finders say the absence of these signs does not establish that a system is unaffected.
[6]
Linux distributions and LTS vendors received the patches in advance, so check your vendor for updated packages.[1]
Updating only the application does not fix the PHP runtime.[6]
Only an update fully fixes these vulnerabilities.[30]
The 34 hours
Times are Eastern (EDT). UTC is four hours later. The release was set for Thursday; PHP moved it up a day after the leak. [2][5][28]
Tue. ~11 AM ET (15:00 UTC): the two CVE IDs began circulating on online forums and social media.
[5] A now-deleted Hacker News post said the flaws would be disclosed on October 22
, as BleepingComputer reported. [28]
Tue. 3:30 PM ET (19:30 UTC): the Foundation says PHP brought its pre-announcement forward and published it at 19:30 UTC.
[5] The notice set the release for Wednesday, 21 October 2026 at 14:00 UTC
and said, We reserve the right to release earlier should details of either vulnerability become public.
[2] BleepingComputer reported it at 4:56 PM ET. [28] The Foundation says it moved the release from October 22nd, 14:00 UTC, to October 21st, 14:00 UTC.
[5]
Tue. ~4 PM ET (around 20:00 UTC): as a result of the leak and pre-announcement,
Calif mistakenly published a video
of its exploits working, per the PHP Foundation. [5]
Tue. 11:02 PM ET (03:02 UTC Wed.): Cloudflare’s rules on by default. [12]
Wed. 3:41 AM ET (07:41 UTC): more than six hours before the coordinated release,
Chainguard published built images with the fix; the Foundation says it unilaterally broke the embargo.
[5]
Wed. by 5:10 AM ET: NOS, at 11:10 Amsterdam time, lists Dutch government and education sites taken offline as a precaution. [20]
Wed. 7:26 AM and 10:19 AM ET (11:26 and 14:19 UTC): watchTowr reported no exploitation, then attempts in its honeypots, as The Hacker News logged; watchTowr’s own page went up at 14:19 UTC. [16][27]
Wed. 7:51 AM to 2:01 PM ET (11:51 to 18:01 UTC): BambooHR offline, then back online following security patching and validation.
[19]
Wed. 10 AM ET (14:00 UTC): PHP releases 8.5.12, 8.4.27, 8.3.36 and 8.2.35. [1] The Foundation says its team did not identify any functional exploits at the time of release/public disclosure.
[5]
Wed. 9:25 PM ET (01:25 UTC Thu.): Prince’s post. Reuters calls it late Wednesday
; outlets on UTC date it Thursday. [13][29]
How long it lived
trigger the memory_limit request termination in places where an interruption is unsafeand run code on PHP servers. [9] Calif traces its find to that line of research. [8]
back to PHP 5.4are affected. [7]
While fixing one of the issues Quarkslab reported, a PHP core developer contracted by the PHP Foundation found the first signs of the OOM problem behind CVE-2026-109618.Then,
a potential exploit for the OOM problem was theorized, but no concrete vectors were found.[5]
We won’t pretend otherwise: the delay was a structural failure, caused by both the security team’s decision process and its lack of resources.The Foundation says it has since added people, a security team and tools. [5]
Who found it
Ryan Austin
Found Aug. 1 · reported Aug. 11
Joined OpenAI’s Patch the Planet program July 30, where PHP stood out as a high-impact target.
[8]
Modelsdo not reliably begin with obscure twenty-year-old exploitation primitives.[8]
Amy Burnett
Same root cause · more on Sept. 18
OpenAI independently reported the same root cause
as Calif, followed by further attack vectors from OpenAI on September 18th
, the PHP Foundation says. [5]
Sagi Tzadik, Shir Tamari, Nir Ohfeld, Tomer Schwartz
Found Aug. 19 · reported Aug. 24
Used Wiz Atlas, Gemini 4 Argon and GPT-5.6 Sol, by Wiz’s account. [7]
a single researcher completed in a week what previously would have taken a world-class team months of work.[7]
Confirmed Calif’s proof of concept Aug. 15 [8] and acknowledged Wiz’s reports Sept. 21. [7] The three teams worked with the PHP security team and the Gemini team at Google on discovery, coordination and patch verification.
[6]
8.5.12, 8.4.27, 8.3.36 and 8.2.35. [1]
No model is simply capable of unearthing[8]Califall bugswith simple prompts. At least for now.
AI helps the team validate reports and group reports sharing the same root cause, anda person makes every call and works on every patch.[5]The PHP Foundation
Frontier modelshelped work through complex exploit chains and adapt them across different deployments.[6]The three research teams, on php2shell.com
Sources
The grid, the strips, the attack drawing, the attempt chart, the timeline and the ruler are drawn for this story from the sources above. The attempt chart draws Prince’s words as ranges on a log scale. Times are converted from UTC to Eastern (EDT). Translations from Dutch are ours. PHP is a trademark of the PHP Group; Cloudflare, WordPress and the other names are trademarks of their owners. No logos are reproduced.