← The Well·dnsc.ai
DNSCFrom the public record
PHP2Shell · October 22, 2026Understanding the week, from the record

PHP · Cloudflare · Oct. 20 to 22, 2026

PHP fixed two flaws that let anyone on the internet run commands on a website’s server. Cloudflare saw millions of attempts within 12 hours of the fix.

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]

69 of 100

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

A web request can trigger the attack before the site’s own code runs.

PHP the language
A programming language that runs on a website’s server and builds each page before it reaches a visitor’s browser. WordPress, Drupal, Nextcloud and phpMyAdmin are built on it. [22]
Shell the command line
A computer’s command line. Having a shell on a server means being able to type commands on it from far away. PHP2Shell is the name the finders gave the pair. [6]
Remote code execution RCE
Running commands on someone else’s computer over the internet. Unauthenticated means no login first. PHP rates both flaws 9.2 out of 10. [2][3][4]
WAF web application firewall
A filter in front of a site that checks each request and blocks ones that match known attacks. Cloudflare turned on rules for these flaws for its customers, free plans included. [12]
How the attack works. Anyone, anywhere sends requests over the web, with no login. A firewall in front of the site can block known attack patterns, if the site has one. Inside the web server, PHP reads the request; the two flaws are there, and on Apache with mod_php the attack can start before the site’s own code runs. Two things can come out: the attacker’s commands run as the web server’s account, and memory from other visitors’ requests can leak, including passwords, tokens and keys.Anyone, anywhereover the web,no login neededA firewall (WAF)can block knownattack patterns,if the site has oneThe web serverPHP reads the requestThe two flaws are here. On Apachewith mod_php, the attack can startbefore the site’s own code runs.The site’s own codeWordPress, Drupal and the restCommands runthe attacker’s own,as the web server’saccountMemory leaks outpieces of othervisitors’ requests:passwords, tokens,keys How the attack works, top to bottom. Anyone, anywhere sends requests over the web, with no login. A firewall can block known patterns, if the site has one. In the web server, PHP reads the request; the two flaws are there, and on Apache with mod_php the attack can start before the site’s own code runs. Out come the attacker’s commands, run as the web server’s account, and leaked memory from other visitors’ requests: passwords, tokens and keys.Anyone, anywhereover the web, no login neededA firewall (WAF)can block known patterns,if the site has oneThe web serverPHP reads the requestThe two flaws are here. OnApache with mod_php, theattack can start before thesite’s own code runs.The site’s own codeWordPress, Drupal andthe restCommands runthe attacker’sown, as the webserver’s accountMemory leaksother visitors’passwords,tokens, keys
Drawn from PHP’s advisory and the two GitHub advisories [1][3][4]; the leaked items are the ones Wiz lists. [7]
The two flaws, in PHP’s words

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

Thousands of attempts before the fix, millions by that night.

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)
Exploit attempts Cloudflare saw, from its CEO’s post, on a log scale. Thousands in the 10 hours before the announcement; tens of thousands within 45 minutes after it; hundreds of thousands within 2 hours; millions by his post at 9:25 PM Eastern on Wednesday. Cloudflare turned its firewall rules on at 11:02 PM Eastern the night before. PHP’s fix came out at 10 AM Eastern. These are attempts; no source on the record confirms a successful break-in.1,00010,000100,0001 million10 million10 PMTue.4 AMWed.10 AM4 PM10 PMCloudflare’s rules onPHP’s fix outthousands,in the 10 hoursbeforetens of thousands,within 45 minuteshundreds ofthousands,within 2 hoursmillionsby his post,9:25 PM ET
Attempts on Cloudflare’s network, log scale: each step up is ten times more. Each bar spans the range of Prince’s word (thousands is 1,000 to 9,999); his post gives no exact counts. Times are Eastern. [12][13]

Who it reaches

Where PHP runs, and who went offline to patch it.

40of 100

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]

20of 100

of all websites send their traffic through Cloudflare, by Cloudflare’s count; W3Techs measures 27.8. [15][25]

35of 100

PHP sites run version 7 or 5 (26.9 and 7.7), lines that no longer get releases from the PHP project. [1][23]

Taken offline as a precaution, Oct. 21

As each one announced it, or as reported.

  • BambooHRHR and payroll, in the U.S., Canada and Ireland: We know this interrupts essential work, including payroll. [19] midnight ET7:51 AM to 2:01 PMmidnight
  • The NetherlandsMijnOverheid and DigiD (the government’s online services and log-in), the House of Representatives’ site, the National Cyber Security Centre’s own site, the Data Protection Authority, Notubiz (a meeting system used by about 100 municipalities) and several university systems. [20]
  • Finland and JapanFinland’s state IT provider, Valtori, shut government public web services and said 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]
  • University of WashingtonCut network access to systems running vulnerable PHP until each was patched, leaving them running. [22]

What to do

Update PHP on the server, or ask your host whether it has.

PHP: There are no complete mitigations, updating is the only safe choice. [1]

Fixed versions [1][18]
If you runFixed inNote
PHP 8.58.5.12
PHP 8.48.4.27
PHP 8.38.3.36
PHP 8.28.2.35End of life Dec. 31, 2026
7.4 to 8.1no releasePHP posted source patches; some vendors ship fixes
5.4 to 7.3no fixPHP: 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]

If you can’t update today: PHP’s stopgaps

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]

If a host or vendor runs PHP for you

  1. Cloudflare’s advice: ask your hosting provider to apply the fix if it manages PHP. Updating the site’s code or plugins alone does not fix these flaws. [12]
  2. PHP: Linux distributions and LTS vendors received the patches in advance, so check your vendor for updated packages. [1]
  3. A vendor’s fix can carry an older-looking version number. Debian advises looking for the CVE number in the package changelog. [27] Debian’s fixed builds are 8.2.35-1~deb12u1 and 8.4.27-1~deb13u1. [26]

If you run it yourself

  1. Update to a fixed version, then restart Apache, PHP-FPM and any long-running PHP workers. Updating only the application does not fix the PHP runtime. [6]
  2. CISA: find every system running PHP, including PHP built into other software; patch the internet-facing ones first; take systems offline if they can’t be updated right away; a web application firewall may offer partial protection until then. [18] The UK’s cyber agency also says to consider taking a system offline until it is fixed. [31]
  3. CERT-EU: Only an update fully fixes these vulnerabilities. [30]

The 34 hours

From leaked ID numbers to millions of attempts, Tuesday to Wednesday night.

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]

The 34 hours, in Eastern time. Tuesday Oct. 20: about 11 AM, the CVE IDs circulate and a post says disclosure comes Oct. 22; 3:30 PM, PHP posts notice moving the release up to Wednesday 10 AM; about 4 PM, Calif posts a video of its exploit by mistake; 11:02 PM, Cloudflare turns its firewall rules on by default. Wednesday Oct. 21: 3:41 AM, Chainguard ships patched images; by 5:10 AM, Dutch government sites are offline; 7:26 AM, watchTowr has seen no exploitation; 7:51 AM to 2:01 PM, BambooHR is offline, payroll included; 10 AM, PHP releases the fixes; 10:19 AM, watchTowr sees attempts in its honeypots; 9:25 PM, Cloudflare’s CEO posts that attempts reached millions.10 AM4 PM10 PM4 AM10 AM4 PM10 PMTUE. OCT. 20WED. OCT. 21Leak and fixDefendersAttempts seenTaken offline~11 AM: CVEIDs circulate~4 PM: Calif’s videoposted by mistake3:30 PM: PHP’s notice,release moved up to Wed.10 AM: PHP releasesthe fixes11:02 PM: Cloudflare’srules on by default3:41 AM: Chainguardships patched imagesthousands (Prince)7:26 AM: watchTowr,no exploitation seen10:19 AM: watchTowr,attempts in its honeypots9:25 PM: Prince,“millions now”by 5:10 AM: Dutchgovernment sites off7:51 AM to 2:01 PM:BambooHR offline,payroll included The 34 hours, top to bottom, in Eastern time, from the CVE IDs circulating on Tuesday Oct. 20 to Cloudflare’s CEO posting “millions now” at 9:25 PM Wednesday Oct. 21.TUE. OCT. 20~11 AMCVE IDs circulate; a postsays disclosure is Oct. 223:30 PMPHP’s notice: release movedup to Wed. 10 AM~4 PMCalif posts its exploitvideo by mistake11:02 PMCloudflare’s firewall ruleson by defaultWED. OCT. 213:41 AMChainguard ships imageswith the fixby 5:10 AMDutch government sitesoffline7:26 AMwatchTowr: no exploitationseen7:51 AMBambooHR goes offline,payroll included10:00 AMPHP releases the fixes10:19 AMwatchTowr: attempts inits honeypots2:01 PMBambooHR back online9:25 PMCloudflare’s CEO:“millions now”
leak and fixdefendersattempts seentaken offlinehollow: a notice or a none seenSources: [1][2][5][12][13][16][19][20][27][28]
Each time, and where it comes from

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

The affected releases go back to PHP 5.4, from March 2012.

How long it lived. July 2004: a researcher shows that hitting PHP’s memory limit can be used to run code. March 2012: PHP 5.4, the oldest affected release line, comes out. Affected releases run from 5.4 through 8.5, about 14 years. 2024: during an audit, a PHP developer finds the first signs of the memory flaw. Zoomed in on August to October 2026: Aug. 1 to 24, Calif and Wiz find and report it; Sept. 21, PHP acknowledges Wiz’s reports; Oct. 21, the fix is out.20042008201220162020Affected releases: PHP 5.4(March 2012) through 8.5July 2004: a researchershows hitting PHP’smemory limit can run code2024: during an audit,first signs of thememory flawZoom: August to October 2026Aug. 1 to 24: Calif andWiz find it and report itSept. 21: PHP acknowledgesWiz’s reportsOct. 21:fix out
Years run left to right; the dashed box on the axis is the zoomed stretch. [5][7][8][9][10]

Who found it

Three research teams, working with AI models, found it and reported it.

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]

Models do not reliably begin with obscure twenty-year-old exploitation primitives. [8]

OpenAI Codex Security

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]

Wiz Research

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]

The PHP security team

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]

Oct. 21: the fix

8.5.12, 8.4.27, 8.3.36 and 8.2.35. [1]

No model is simply capable of unearthing all bugs with simple prompts. At least for now. [8]Calif
AI helps the team validate reports and group reports sharing the same root cause, and a person makes every call and works on every patch. [5]The PHP Foundation
Frontier models helped work through complex exploit chains and adapt them across different deployments. [6]The three research teams, on php2shell.com

Sources

  1. The PHP Group, “Security advisory: Critical remote code execution vulnerabilities, update now,” and the PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 release notes, Oct. 21, 2026, php.net/archive/2026.php, read Oct. 22, 2026.
  2. The PHP Group, “Upcoming Critical PHP Security Release,” Oct. 20, 2026, php.net/archive/2026.php.
  3. PHP security advisory GHSA-w8hw-w9fx-j79w, “RCE via OOM corruption,” CVE-2026-109618, Oct. 21, 2026, github.com/php/php-src.
  4. PHP security advisory GHSA-6wmf-4rv5-p3rp, “RCE via stale global state,” CVE-2026-109619, Oct. 21, 2026, github.com/php/php-src.
  5. The PHP Foundation, “Today’s PHP Security Release, and How We’re Strengthening PHP Security,” Oct. 21, 2026, thephp.foundation/blog.
  6. Wiz Research, Calif and OpenAI Codex Security, “PHP2Shell,” php2shell.com, read Oct. 22, 2026.
  7. Sagi Tzadik, Shir Tamari, Nir Ohfeld and Tomer Schwartz, Wiz Research, “PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet,” Oct. 21, 2026, wiz.io/blog.
  8. Calif, “php2shell,” calif.io/php2shell, read Oct. 22, 2026.
  9. Stefan Esser, “Advisory 11/2004: PHP memory_limit remote vulnerability,” Bugtraq, July 14, 2004, marc.info.
  10. The PHP Group, PHP 5 ChangeLog, “Version 5.4.0, 01 Mar 2012,” php.net/ChangeLog-5.php.
  11. The PHP Group, home page, php.net, read Oct. 22, 2026.
  12. Cloudflare, “Cloudflare deploys protections against php2shell vulnerability,” Oct. 21, 2026, blog.cloudflare.com.
  13. Matthew Prince, post on X, x.com/eastdakota; text as printed by OfficeChai, Oct. 22, 2026 (officechai.com) and Reuters [29]. The post time, 01:25 UTC Oct. 22, is read from the post’s ID.
  14. Mirko Zorz, Help Net Security, “PHP2Shell: Critical PHP vulnerabilities patched, update now!,” Oct. 21, 2026, updated Oct. 22, helpnetsecurity.com: Dane Knecht’s post on X (x.com/dok2001).
  15. Cloudflare, “Application services,” cloudflare.com/application-services, read Oct. 22, 2026.
  16. watchTowr, “PHP Remote Code Execution (PHP2Shell),” Oct. 21, 2026, 14:19 UTC, watchtowr.com, and “PHP RCE FAQ,” Oct. 20, 2026, watchtowr.com.
  17. CJ Moses, Amazon, “Amazon threat intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot,” Oct. 21, 2026, aws.amazon.com/blogs/security.
  18. Cybersecurity and Infrastructure Security Agency, “Critical Vulnerabilities in PHP Require Immediate Patching,” Oct. 21, 2026, cisa.gov.
  19. BambooHR status page, “BambooHR Temporarily Unavailable: Security Precaution,” Oct. 21, 2026, status.bamboohr.com.
  20. NOS, “Websites van overheid en in onderwijs offline vanwege lek, risico op hacks,” Oct. 21, 2026, nos.nl (in Dutch).
  21. NOS, “Signalen bij Nationaal Cyber Security Centrum van misbruik PHP-lek,” Oct. 22, 2026, nos.nl (in Dutch).
  22. University of Washington IT, “PHP CVEs,” updated Oct. 22, 2026, it.uw.edu.
  23. W3Techs, “Usage statistics of PHP for websites,” data of Oct. 22, 2026, w3techs.com.
  24. W3Techs, “Usage statistics of WordPress,” data of Oct. 22, 2026, w3techs.com.
  25. W3Techs, “Usage statistics of Cloudflare,” October 2026, w3techs.com.
  26. Debian security tracker, CVE-2026-109618, security-tracker.debian.org, read Oct. 22, 2026.
  27. Swati Khandelwal, The Hacker News, “PHP Issues Emergency Patches for Two Critical PHP2Shell RCE Flaws as Exploit Attempts Emerge,” Oct. 21, 2026, thehackernews.com.
  28. Lawrence Abrams, BleepingComputer, “PHP warns admins of two critical flaws, emergency patches coming tomorrow,” Oct. 20, 2026, 4:56 PM ET, bleepingcomputer.com.
  29. Eduardo Baptista, Toby Sterling and Mariko Katsumura, Reuters, “Cloudflare sees millions of exploit attempts after PHP disclosure,” Oct. 22, 2026, via globalbankingandfinance.com.
  30. CERT-EU, Security Advisory 2026-018, Oct. 21, 2026, cert.europa.eu.
  31. UK National Cyber Security Centre, “Critical security issue affecting PHP,” Oct. 21, 2026, ncsc.gov.uk.

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.