A Long Road To PHP2Shell: What AI-Assisted Review Contributed
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: A Long Road To PHP2Shell: What AI-Assisted Review Contributed on ThorstenMeyerAI.com

Buying for a business?Offer from Amazon

Get business pricing on office and shipping supplies

  • Business-only prices and quantity discounts
  • Tax-exempt purchasing
  • Multiple users, one account, clear invoices
As an affiliate, we earn on qualifying purchases.

TL;DR

PHP released fixes on October 21, 2026, for two critical remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell. Researchers at Calif and Wiz independently found flaws in the same class, with AI tools contributing to parts of the research; Calif’s account traces the underlying risk back to a 2004 warning about unsafe interruptions.

PHP shipped fixes on October 21, 2026, for two critical remote code execution flaws, CVE-2026-109618 and CVE-2026-109619, now known as PHP2Shell. A retrospective published by Thorsten Meyer on October 22 says researchers at Calif and Wiz found vulnerabilities in the same broad class, with AI tools assisting parts of their work; the account traces the security concern to a warning first published in 2004.

According to the retrospective, Calif reported its first bug to PHP on August 11, shared a working proof of concept on August 14, and received confirmation from PHP the following day. Calif reported a second bug on August 21. The account says the team found several independent paths to remote code execution on August 1, though it does not provide the technical details needed to assess each path independently.

Wiz Research worked in parallel and, according to its disclosure post as summarized by Meyer, found its first PHP vulnerability on August 19. Wiz said it validated unauthenticated code execution against Drupal on August 20 and WordPress on August 21, then reported the issue to PHP on August 24. Wiz and Google’s security blog credited Gemini 4 Argon with contributions to finding the vulnerability, exploit development, attack detection and patch validation.

The reported discovery process involved researcher-led investigation alongside AI tools, not an automated search for every possible bug. Calif’s Ryan Austin said he selected a target he knew and drew on its vulnerability history to guide the work. The retrospective says Calif used no special harness and no models beyond those generally available. OpenAI said Calif used GPT-5.6 Sol through its Patch the Planet initiative. These are the organizations’ descriptions of their work; PHP’s fixes are the confirmed outcome.

At a glance
reportWhen: Fixes shipped October 21, 2026; the acc…
The developmentPHP shipped fixes for two critical remote code execution flaws on October 21, after separate Calif and Wiz research efforts identified vulnerabilities linked to unsafe out-of-memory handling.
Thorsten Meyer AI
2004 → 2026

Infographic 01 · Timeline

One class of bug, four chances to catch it.

The flaws fixed on 21 October 2026 continue a line that starts with a 2004 advisory about unsafe interruptions.

22years from the 2004 advisory to the 2026 fix
2CVEs, both rated 9.2 (CVSS v4.0)
3research groups credited: Calif, OpenAI, Wiz
4fixed PHP branches on 21 Oct 2026
  1. Jul 2004
    Stefan Esser: memory_limit can stop PHP “where an interruption is unsafe”Advisory 11/2004, CAN-2004-0594. Remote code execution was possible. (e-matters)
  2. 28 Nov 2019
    Bug #78876: long upload fields cause out-of-memory, temp files left behindFixed May 2020 as CVE-2019-11048, a denial-of-service issue at the time. (PHP bug tracker)
  3. 2024
    Quarkslab audit with OSTIF and the PHP FoundationAccording to Calif, it rediscovered the same OOM issue; exploitation was not proven, so it stayed open. (Calif, OSTIF)
  4. 30 Jul 2026
    Calif joins OpenAI’s Patch the Planet and picks PHPStefan Esser brings in the PHP Foundation through Volker Dusch. (Calif)
  5. 1–21 Aug 2026
    Calif finds several RCE paths and reports two bugs to PHPFirst report 11 Aug, working proof of concept 14 Aug, confirmed by PHP 15 Aug, second report 21 Aug. (Calif)
  6. 19–24 Aug 2026
    Wiz Research finds its first PHP flaw and reports on 24 AugUsing Wiz Atlas, Gemini 4 Argon and GPT-5.6 Sol; RCE confirmed on Drupal and WordPress. (Wiz)
  7. 21 Oct 2026
    PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 releasedCVE-2026-109618 and CVE-2026-109619, both CVSS v4.0 9.2. Public disclosure the same day. (PHP)

“…possible for a remote attacker to trigger the memory_limit request termination in places where an interruption is unsafe.”Stefan Esser, e-matters Advisory 11/2004

Sources: e-matters Advisory 11/2004; PHP bug #78876; OSTIF; Calif: php2shell; Wiz Research (21 Oct 2026); PHP security advisory (21 Oct 2026).
Powered by Thorsten Meyer AI

What PHP Users Need to Know

Remote code execution flaws can allow an attacker to run code on a vulnerable server, making the PHP fixes relevant to operators of applications built on the runtime. Wiz reported validating unauthenticated code execution against Drupal and WordPress, underscoring the potential reach of a flaw in a widely used software component. The supplied account does not establish how many systems were vulnerable or whether attackers exploited the issues before the fixes.

The history also illustrates why AI assistance does not remove the need for security expertise. Calif’s account says Austin’s familiarity with older vulnerabilities helped direct the search toward an obscure failure pattern. Models supported aspects of the investigation, but the researcher supplied the hypothesis and judgment. That distinction matters as maintainers and security teams evaluate claims about what AI can and cannot find.

Bose QuietComfort Wireless Noise-Cancelling Headphones, Sandstone

Bose QuietComfort Wireless Noise-Cancelling Headphones, Sandstone

Breville BES870BSXL Barista Express Espresso Machine, Black Sesame

Breville BES870BSXL Barista Express Espresso Machine, Black Sesame

Bose QuietComfort Headphones (2nd Gen), Wireless Noise-Cancelling Over-Ear Headphones, Eucalyptus Green

Bose QuietComfort Headphones (2nd Gen), Wireless Noise-Cancelling Over-Ear Headphones, Eucalyptus Green

As an affiliate, we earn on qualifying purchases.

From a 2004 Warning to PHP2Shell

In July 2004, security researcher Stefan Esser published an advisory warning that PHP’s memory limit could terminate a request at a point where interruption was unsafe. Esser said an attacker might use this behavior to run code on remote PHP servers. PHP fixed the specific paths he reported, but the broader concern—what can happen when execution stops during an incomplete operation—remained relevant to later research.

A PHP bug report filed in November 2019 described large multipart form fields causing out-of-memory failures and leaving temporary upload files behind. PHP fixed the issue in May 2020 as a denial-of-service problem, assigned CVE-2019-11048. Calif’s account presents that report as a clue about the consequences of memory exhaustion, not as proof that the later remote code execution flaws had already been established.

Calif also says a 2024 audit rediscovered the out-of-memory issue but did not prove exploitability. The published audit summary, according to Meyer, listed 27 findings and four CVEs but did not mention that issue. The 2026 research then returned to the older class of concern as part of an effort to harden critical open-source software.

““possible for a remote attacker to trigger the memory_limit request termination in places where an interruption is unsafe””

— Stefan Esser, in his July 2004 advisory as quoted by Meyer

Exploit Activity and Scope Remain Unknown

The supplied account does not say whether either PHP2Shell vulnerability was exploited in the wild, how many installations were exposed, or which PHP versions and configurations were affected. It also does not include the PHP security team’s technical advisory or enough vulnerability detail to independently compare the two CVEs. Calif’s description of the 2024 audit finding is attributed to the research team; the audit summary cited by Meyer does not mention that issue.

The exact division of work between researchers and AI systems is not fully detailed in the material. Calif, OpenAI, Wiz and Google describe contributions to discovery and validation, but those accounts do not establish that AI tools independently identified or verified the flaws. Claims about the breadth of the affected software ecosystem should be read alongside PHP’s technical guidance.

Patch Deployment and Technical Guidance

PHP operators should consult the PHP security team’s advisories for the affected versions and upgrade instructions, then apply the available fixes. The source account confirms that fixes shipped on October 21 but does not specify the patched version numbers. Administrators should verify those details against PHP’s release information before planning deployment, and check application and server logs for signs of suspicious activity according to their incident-response procedures.

Further clarity depends on the technical disclosures from PHP, Calif and Wiz, including affected configurations, patch details and any evidence of exploitation. The retrospective’s next practical step for readers is its separate patch, restart and verification guide; it does not provide those operational instructions in the supplied material.

Key Questions

What is PHP2Shell?

PHP2Shell is the name used for two critical remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619, for which PHP shipped fixes on October 21, 2026.

Who found the PHP2Shell flaws?

The account describes separate research by Calif and Wiz Research. Calif reported bugs to PHP in August 2026, while Wiz says it found a vulnerability independently and reported it later that month.

What did AI contribute to the research?

Calif and OpenAI said GPT-5.6 Sol assisted Calif’s work; Wiz and Google credited Gemini 4 Argon with contributions to discovery, exploit development, attack detection and patch validation. The account presents the research as guided by human researchers, and does not say AI found every relevant flaw on its own.

Were the vulnerabilities exploited in real attacks?

The supplied reporting does not establish whether attackers exploited PHP2Shell before the fixes. The scale of exposure and any confirmed incidents remain unclear.

What should PHP administrators do?

Check the PHP security team’s advisories for the affected versions and patched releases, then apply the relevant update. The source account confirms fixes were shipped but does not list version numbers.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

AI And Interactive Art: An Examination Of ‘Lot 87 — The Varos Evening Sale’

An in-depth look at how AI and custom coding transformed the auction of ‘Lot 87,’ creating an immersive, interactive experience that redefines cultural events.

10 Best 4K Webcams To Bring Clarity To Professional Video In 2027

A ThorstenMeyerAI.com buying guide compares 10 4K webcams by image quality, lighting, autofocus, privacy features and software support.

Entertainment signal monitor: Toy Story 5

Toy Story 5 is now detected in entertainment signal monitoring tools, indicating early development or announcement. This development is crucial for industry operators.