What PHP patched on 21 October

On 21 October the PHP project released 8.5.12, 8.4.27, 8.3.36 and 8.2.35, closing two memory-safety flaws in the core engine. Both are rated 9.2, CVE-2026-109618 and CVE-2026-109619, and both allow unauthenticated remote code execution (an attacker runs code on the server without logging in) and process-memory disclosure. Wiz Research calls them PHP2Shell, a critical flaw in PHP, and its write-up traces the vulnerable pattern back to every release from 5.4. W3Techs puts PHP on 69.3% of websites whose server-side language it knows; Wiz headlines 70% of the internet in its write-up.

What the two flaws do

A memory-safety bug is code reading or writing memory it no longer owns. In CVE-2026-109618, an out-of-memory error can interrupt PHP while request data is only partly built, and cleanup then treats the invalid data as valid. In CVE-2026-109619, internal state can outlive the memory behind it, and the next request on the same worker may use the stale copy. Wiz counts four exploitable bugs under the two CVEs. The Foundation adds that “in 2024, a potential exploit for the OOM problem was theorized, but no concrete vectors were found and other concrete issues with clear impact overshadowed these concerns.”

Who found it, and who says so

Four accounts disagree. Wiz credits Wiz Atlas working with Gemini 4 Argon and GPT-5.6 Sol, dating discovery to 19 August and the report to PHP to 24 August. OpenAI’s account says “Calif identified a critical flaw using GPT-5.6 Sol… with Wiz also independently discovering and reporting both vulnerabilities”. Calif’s write-up names Ryan Austin, dates discovery to 1 August, and says the find used no special harness and no models beyond generally available ones. The PHP Foundation records that Calif reported on 11 August, that OpenAI independently reported the same root cause that day, and that Wiz followed on 24 August. Wiz says the findings “rank among the most severe vulnerabilities discovered in PHP, and arguably in software history”; OpenAI calls them one of the most impactful security issues in recent memory. Both are vendor assessments, and OpenAI also promotes its “Defender’s Window” framing, a $1 billion Daybreak subsidy and a proposed disclosure framework, which are programme material, not evidence.

Why exploitation still needs a chain of conditions

Both advisories score Attack Complexity as High with Attack Requirements Present: two requests must reach the same worker, and unrelated traffic can increase the number of attempts an attacker needs. Wiz describes the exploit as “at the edge of what human researchers could practically achieve”, requiring a chain of flaws and adaptation to each target’s memory layout. Wiz adds that with AI this is “no longer a barrier”; The Verge calls the exploit “relatively trivial” once the flaws were public. Both are framings, not an independent measurement.

Honeypot and WAF sightings, but no confirmed mass compromise

A public exploit tool combines both bugs into one attack that needs no login, according to Sansec. watchTowr reports in-the-wild exploitation through its honeypots from 21 October, and CISA’s KEV catalogue did not list either CVE as of 22 October. Cloudflare reports attack traffic and payload mutation, and the PHP Foundation found no functional exploits at release. No victim count exists.

What to do if you run a site

Check the version you are actually running, through cPanel or Plesk, or WordPress’s Tools > Site Health > Info panel. The fixed releases are 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older no longer receive official fixes from the PHP project, though some providers backported one. Providers that backported the fix onto the previous release kept the version number the same; GoDaddy tells its shared-hosting customers to check the build date, 21 October 2026 or later. If you cannot update, the NSA advised organisations to “take the system offline until it can be fully mitigated”, in a 21 October press release read through a Wayback capture because the live page returned an error. On managed hosting, ask your provider to apply the fix.

The bill nobody advertises

Applying the fix is human work on timetables nobody publishes. GoDaddy’s status log shows managed WordPress hosting patched at 19:30 UTC on 21 October, Windows hosting at 01:20 UTC the next day, and all Web Hosting PHP versions patched on 22 October. On managed plans the owner does nothing; on a VPS the owner is the patch team. VirusTotal found that roughly four out of five internet-facing PHP servers do not announce a version, so the owner-side check is the reliable one. Wikimedia took Toolforge and Cloud VPS offline because volunteers control those services’ PHP version, warning they “may be offline for longer”. The PHP Foundation says its security work “still depends on a small group of foundation-funded developers and a little volunteer help”, and asks hosts and governments to fund it. GoDaddy sells Expert Services to apply the update, and Cloudflare, Sansec and watchTowr promote their own detection products.

What to watch next

Whether exploitation escalates beyond the honeypot and WAF sightings, whether CISA adds either CVE to KEV, and how many unsupported 8.1-and-older installs ever get a fix.