🔍 Read the full analysis: What Happens When AI-Assisted Review Meets A 22-Year-Old PHP Story? on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
PHP released fixes on Oct. 21, 2026, for two critical remote code execution flaws identified as CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell. The account links the research to a 2004 warning about unsafe interruptions, a later out-of-memory bug report and AI-assisted work by Calif and Wiz; some details of the vulnerabilities and their impact remain unclear in the supplied material.
PHP shipped fixes on October 21, 2026, for two critical remote code execution flaws, CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell. The discovery story reaches back to a 2004 warning about PHP memory-limit interruptions and includes AI-assisted research by Calif and Wiz, but the supplied account does not detail the final patches or establish how widely the flaws were exploitable in deployed systems.
The account traces one strand of the issue to Stefan Esser’s July 2004 advisory, which warned that a remote attacker could trigger PHP’s memory-limit termination at a point where interruption was unsafe. The concern was that cleanup after an interrupted operation could encounter a partly built structure. PHP fixed the specific paths Esser identified, while the broader problem of interruption at unsafe moments remained a research question.
A later clue appeared in PHP bug report #78876, filed on November 28, 2019. It described large multipart form fields causing an out-of-memory condition and leaving temporary files from earlier uploads in the same request. PHP fixed the reported issue in May 2020; it was classified as a denial-of-service vulnerability, CVE-2019-11048, because remaining files could consume disk space. Calif’s account says the report prompted researchers to ask what else might persist after an out-of-memory event.
According to the supplied timeline, Calif reported a first flaw to PHP on August 11, 2026, sent a proof of concept on August 14, and received confirmation the following day. It reported a second flaw on August 21. Wiz Research worked independently, finding a PHP vulnerability on August 19 and reporting it to PHP on August 24, according to its disclosure post. PHP issued fixes for the two critical flaws on October 21. The source credits Calif, OpenAI and Wiz with the research, and the PHP security team with the fixes.
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.
- Jul 2004Stefan Esser: memory_limit can stop PHP “where an interruption is unsafe”Advisory 11/2004, CAN-2004-0594. Remote code execution was possible. (e-matters)
- 28 Nov 2019Bug #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)
- 2024Quarkslab 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)
- 30 Jul 2026Calif joins OpenAI’s Patch the Planet and picks PHPStefan Esser brings in the PHP Foundation through Volker Dusch. (Calif)
- 1–21 Aug 2026Calif 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)
- 19–24 Aug 2026Wiz 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)
- 21 Oct 2026PHP 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
Why PHP’s Old Warning Matters
The episode matters because PHP runs a large share of the web, so remote code execution flaws can put applications built on the runtime at risk. The source identifies Drupal and WordPress as systems against which Wiz confirmed unauthenticated code execution during its testing. That is evidence of demonstrated impact in those tests, not a measure of how many live sites were vulnerable or compromised.
The account also offers a grounded view of AI-assisted security work. AI tools supported searches and testing, but the research described was directed by people familiar with PHP’s history and vulnerability patterns. The connection to a 22-year-old warning is presented as a research lead, not proof that the 2004 advisory described the exact 2026 flaws. For maintainers, the immediate issue is the PHP fix; for security teams, the broader lesson is that old, unresolved classes of failure can guide new reviews.
Popular right now

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

Dyson Cyclone V10 Origin Cordless Vacuum

KitchenAid 5.5-Quart Bowl-Lift Stand Mixer, Porcelain White
As an affiliate, we earn on qualifying purchases.
From Memory Limits to PHP2Shell
In 2004, Esser’s advisory, titled “PHP memory_limit remote vulnerability,” said it was possible for an attacker to cause request termination where interruption was unsafe, potentially enabling code execution. PHP fixed the specific paths then reported. The later 2019 bug report concerned a distinct, documented effect of running out of memory: temporary files left on disk. It was fixed as a denial-of-service issue in 2020.
A 2024 PHP audit by Quarkslab, OSTIF and the PHP Foundation listed 27 findings and four CVEs, which the source says were resolved. Calif’s account says auditors rediscovered the out-of-memory issue, but exploitation was not proven and the issue was not fixed at that time. OSTIF’s published summary, as described in the source, does not mention that issue. The claims about the audit should therefore be attributed to Calif, rather than treated as independently confirmed by the summary.
In July 2026, Calif joined OpenAI’s Patch the Planet initiative and selected PHP for research. Calif researcher Ryan Austin said he chose a target whose vulnerability history he knew and worked from a theory about where bugs might remain. The account says the work used no special harness and no models beyond those generally available. Calif and Wiz then reported findings through separate disclosure timelines in August.
““No model is simply capable of unearthing ‘all bugs’.””
— Ryan Austin, in Calif’s write-up
What the Disclosure Leaves Open
The supplied material does not describe the exact code paths in either PHP2Shell flaw, the technical differences between the two CVEs, or which PHP releases were affected. It also does not say whether attackers exploited the vulnerabilities before the fixes, how many installations were exposed, or whether the fixes require additional configuration changes. Those details should not be inferred from the researchers’ successful testing against Drupal and WordPress.
The link between the 2004 advisory, the 2019 out-of-memory report and the 2026 vulnerabilities is a historical and investigative account from Calif, not a full technical comparison in the material provided. Calif’s description of what auditors saw in 2024 also differs from the omission in OSTIF’s public summary. The precise status of that audit finding, and whether it was directly related to either 2026 CVE, remains unclear here.
Patch Status and Technical Details
PHP has shipped fixes, and operators should consult the PHP security team’s official advisories and release notes for affected versions, patch instructions and any required follow-up. The source points readers to a separate patch-and-restart guide, but does not provide its steps or identify the fixed release numbers. Until those specifics are checked against official PHP guidance, this account cannot establish whether a particular server is protected.
Further technical disclosures from PHP, Calif and Wiz may clarify the flaws’ scope, the relationship between the historical reports and the CVEs, and any evidence of exploitation. The next practical milestone for administrators is confirming their installed PHP version against the official fixed-version list and applying the appropriate update.
Key Questions
What is PHP2Shell?
PHP2Shell is the name used in the source for two critical remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619, for which PHP shipped fixes on October 21, 2026.
Did AI find the PHP vulnerabilities on its own?
No. The account describes AI tools as part of researcher-led work. Calif’s Ryan Austin selected PHP and directed the investigation using knowledge of the runtime’s history; Wiz also reported using its platform and AI models in its research.
Were the vulnerabilities exploited in real-world attacks?
The supplied material does not say whether attackers exploited the flaws before PHP released fixes. Wiz’s testing reportedly confirmed unauthenticated code execution against Drupal and WordPress, but that does not establish exploitation of live systems.
How does the 2004 advisory relate to the 2026 flaws?
The advisory warned that PHP memory-limit termination could occur at an unsafe point. Calif’s account presents it as an early warning and research clue; the material does not provide enough technical detail to confirm that the 2026 CVEs are the same vulnerability or code path.
What should PHP operators do now?
Check PHP’s official security advisories and release notes for affected versions, then apply the fix for the version in use. The supplied source does not list the fixed release numbers or patch commands.
Source: ThorstenMeyerAI.com
