AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

PHP released fixes on Oct. 21, 2026, for two remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619, both rated 9.2 under CVSS v4.0. Calif, OpenAI and Wiz are credited with research that exposed the flaws; Calif’s account traces a related memory-handling problem to a 2004 advisory, though the relationship between the earlier bug and the newly fixed vulnerabilities requires careful distinction.

PHP released security updates on Oct. 21, 2026, fixing two remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619, each rated 9.2 under CVSS v4.0. The flaws, referred to as PHP2Shell, were reported by researchers credited to Calif, OpenAI and Wiz, and affect a runtime used across a large portion of the web.

The fixes are included in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP’s security advisory disclosed the vulnerabilities on the release date. Calif’s account says its researchers reported the first issue on Aug. 11, produced a working proof of concept on Aug. 14, and received confirmation from PHP on Aug. 15. Calif reported a second issue on Aug. 21. Wiz Research separately reported its first PHP flaw on Aug. 24, after research beginning Aug. 19.

Buying for a business?Offer from Amazon

Get business pricing on tech for your team

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

The published account describes a line of investigation involving out-of-memory behavior and unsafe interruption in PHP. It links that history to a 2004 advisory and a 2019 bug report, but those earlier records had distinct findings and outcomes. The 2019 issue, fixed in 2020 as CVE-2019-11048, was treated as a denial-of-service problem involving leftover temporary files. The available material does not establish that the 2004 vulnerability, the 2019 issue and the 2026 CVEs are identical vulnerabilities.

Calif’s write-up credits research by Calif, OpenAI and Wiz, with the fixes made by the PHP security team. It says Wiz used Wiz Atlas alongside Gemini 4 Argon and GPT-5.6 Sol, and that remote code execution was confirmed on Drupal and WordPress. These are details reported by the research accounts; PHP’s release notice is the source for the patched versions and CVE identifiers.

At a glance
updateWhen: PHP releases published Oct. 21, 2026; v…
The developmentPHP published security releases fixing two critical remote code execution vulnerabilities after research credited to Calif, OpenAI and Wiz.
The PHP2Shell Journey: 22 Years and a New AI-Assisted Review

Security timeline · PHP · October 2026

The PHP2Shell Journey: 22 Years and a New AI-Assisted Review

Two high-severity remote code execution flaws were patched in PHP. Research accounts connect the investigation to a longer history of memory-handling concerns, while the public record leaves key technical links unresolved.

“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

The historical thread is useful context. It does not establish that the 2004, 2019 and 2026 findings are the same vulnerability.

2Remote code execution CVEs
9.2CVSS v4.0 rating each
Oct 21PHP security releases
4Patched PHP branches

01 / At a glance

What happened

PHP disclosed and fixed two vulnerabilities referred to in the reporting as PHP2Shell. Research credit is attributed to Calif, OpenAI and Wiz; PHP’s security team issued the fixes.

The findings

Two CVEs, one release date

CVE-2026-109618 and CVE-2026-109619 are both described as remote code execution flaws and rated 9.2 under CVSS v4.0.

The impact

Server-side exposure

Remote code execution can let an attacker run code on a vulnerable server, depending on exploit conditions and system configuration.

The response

Updates are available

Administrators should identify their active PHP branch, install its corresponding fixed release, and verify services use the updated runtime.

02 / The long view

Calif’s account traces a research journey across memory limits and out-of-memory behavior. Each milestone had its own finding and outcome.

01

Memory limit advisory

Stefan Esser’s advisory described unsafe request interruption and a possible remote code execution consequence. PHP fixed the reported paths.

02

Bug report #78876

Long multipart fields could trigger an out-of-memory condition and leave temporary files behind.

03

Denial-of-service fix

The 2019 report was fixed as CVE-2019-11048 and described as a denial-of-service issue.

04

Audit revisits the issue

Calif says an out-of-memory issue was seen during a PHP audit; exploitation was not proven. The public summary cited does not mention it.

05

Research and patches

Calif and Wiz reported findings in August. PHP published security releases on October 21.

Keep distinct

The available material does not establish that the 2004 advisory, the 2019 denial-of-service issue and the two 2026 CVEs share one underlying defect or a continuous exploit path.

03 / Administrator action

Patch the deployed branch

The PHP release information lists fixes in these versions. Confirm the runtime serving production traffic has been updated.

8.5.12PHP 8.5 branch
8.4.27PHP 8.4 branch
8.3.36PHP 8.3 branch
8.2.35PHP 8.2 branch

04 / Research path

From investigation to release

The timeline below summarizes the sequence described in the research accounts. PHP’s release notice confirms the patched versions and CVE identifiers.

1

Choose a target

Calif joined OpenAI’s Patch the Planet program on July 30, 2026, and selected PHP for research.

2

Report findings

Calif’s account dates its first report to August 11 and a second to August 21. Wiz separately reported a PHP flaw on August 24.

3

Confirm and test

Calif reports PHP confirmed the first issue on August 15. Research accounts describe testing; Wiz reported RCE confirmation on Drupal and WordPress.

4

Release fixes

PHP published security updates on October 21, 2026. The supplied material does not give a patching deadline.

05 / Evidence boundaries

What remains open

The public material supports a clear patch recommendation, but leaves the scale and technical details of exposure unsettled.

Technical conditions

The supplied information does not detail the precise conditions required to exploit each 2026 CVE.

Exposure in the wild

It does not establish how many systems remain unpatched or whether attacks have been observed in the wild.

Historical relationship

Memory-limit and out-of-memory concerns recur in the accounts, but the relationship among the separate vulnerabilities is unproven.

Research attribution

Calif’s write-up credits Calif, OpenAI and Wiz. It says Wiz used Wiz Atlas alongside Gemini 4 Argon and GPT-5.6 Sol.

06 / Quick answers

Key questions

A concise guide to the names, fixes and limits of what is currently reported.

What is PHP2Shell?

The name used in the supplied reporting for CVE-2026-109618 and CVE-2026-109619, two PHP remote code execution vulnerabilities, each rated 9.2 under CVSS v4.0.

Which versions contain the fixes?

PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, according to the October 21 release information.

Who found the vulnerabilities?

The research is credited to Calif, OpenAI and Wiz. PHP’s security team issued the fixes.

Are the older issues the same flaws?

The supplied material does not establish that. The 2019 issue was fixed as CVE-2019-11048 and described as denial of service.

Are attacks confirmed?

The supplied material does not say whether PHP2Shell has been exploited in the wild or quantify remaining exposure.

What should operators do?

Identify the PHP branch in service, install its corresponding patched release, then confirm production services use the updated runtime.

What PHP Users Need to Know

The flaws matter because remote code execution can allow an attacker to run code on a vulnerable server, subject to the conditions of the exploit and the server’s configuration. PHP’s release of patched versions gives administrators a direct remediation path. Operators should identify which PHP branch they run, apply its corresponding update, and check that the updated runtime is in service.

The episode also shows how a security issue can develop across research efforts and over time. Calif’s account connects its investigation to an older class of memory-limit interruption problems, while the 2024 audit account is qualified: Calif says the issue was seen again, but exploitation was not proven at that time. That history offers a reason to revisit unresolved signals, but it does not by itself prove a continuous exploit path spanning all the events.

Products Worth Considering

Jackery HomePower 3600 Plus Portable Power Station, 3584Wh, 3600W

Jackery HomePower 3600 Plus Portable Power Station, 3584Wh, 3600W

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite

As an affiliate, we earn on qualifying purchases.

From Memory Limits to PHP2Shell

In July 2004, security researcher Stefan Esser published e-matters Advisory 11/2004, titled “PHP memory_limit remote vulnerability.” The advisory said a remote attacker could trigger request termination where interruption was unsafe and described remote code execution as a possible consequence. PHP fixed the specific paths Esser reported, according to the source material.

On Nov. 28, 2019, PHP’s bug tracker received report #78876, concerning long multipart form fields that could cause an out-of-memory condition and leave temporary files behind. PHP fixed the issue in May 2020; it became CVE-2019-11048, classified in the supplied account as denial of service. In 2024, Quarkslab audited PHP with OSTIF and the PHP Foundation. Calif says the audit rediscovered the out-of-memory issue, but that exploitation was unproven. The supplied material notes that OSTIF’s public summary does not mention that issue.

Calif joined OpenAI’s Patch the Planet program on July 30, 2026, and selected PHP for research. The account says Stefan Esser connected the effort with the PHP Foundation through Volker Dusch. During August, Calif and Wiz reported separate findings to PHP. The project’s illustrated retelling is based on Calif’s write-up; its research and write-up are credited to Ryan Austin, with comic story and poster by Michal Zalewski and illustrations by Stephanie Cortes of Ibis Craft.

““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

What the Public Record Leaves Open

The material available here does not detail the precise technical conditions for exploiting each 2026 CVE, how many systems remain unpatched, or whether attacks have been observed in the wild. It also does not establish that the 2004 advisory, the 2019 denial-of-service issue and the 2026 remote code execution flaws share the same underlying defect. Calif’s account says the 2024 audit encountered a related out-of-memory issue, while stating that exploitation was not proven; the public audit summary cited in the source does not mention that issue.

The research accounts describe testing and findings, but the supplied material does not include independent reproduction details for every claim. PHP’s patched release versions and CVE disclosures are confirmed in the cited security release information; broader claims about the vulnerabilities’ technical lineage and research process should remain attributed to the researchers.

Patch Rollout and Further Disclosure

PHP administrators can move to the patched release for their supported branch: 8.5.12, 8.4.27, 8.3.36 or 8.2.35. The next practical step for operators is to verify which version is deployed and confirm that services use the updated runtime after rollout. The supplied source material does not give a deadline for patching or report how quickly deployments are progressing.

Further technical detail may come from PHP’s advisories and the research groups’ write-ups. Until more information is published, the scope of exposure, the prevalence of vulnerable deployments and any evidence of exploitation remain unresolved.

Key Questions

What is PHP2Shell?

PHP2Shell is the name used in the supplied reporting for two PHP remote code execution vulnerabilities: CVE-2026-109618 and CVE-2026-109619. Both were rated 9.2 under CVSS v4.0.

Which PHP versions include the fixes?

The fixes were released in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, according to the Oct. 21, 2026 release information.

Who found the vulnerabilities?

The research is credited to Calif, OpenAI and Wiz. The supplied accounts describe separate reports during August 2026; PHP’s security team issued the fixes.

Are the 2026 flaws the same as the 2004 and 2019 issues?

The source material traces a history of memory-limit and out-of-memory concerns, but does not establish that the earlier findings and the 2026 CVEs are the same vulnerability. The 2019 issue was fixed as CVE-2019-11048 and was described as a denial-of-service problem.

Are attacks using PHP2Shell confirmed?

The supplied material does not say whether the vulnerabilities have been exploited in the wild or how many systems remain exposed. It reports that Wiz confirmed remote code execution in testing on Drupal and WordPress.

Source: Thorsten Meyer AI

You May Also Like

What’s Confirmed About The TSMC Employee Data Breach—and What’s Claimed

TSMC says employee data appeared online and matched a cloud provider’s records. The seller’s 46,000-record figure and data details remain unverified.

Navigating AI’s Path To Astra: Key Capabilities And Safety Measures

OpenAI’s ‘Path to Astra’ page highlights focus on advanced capabilities and safeguards, but details on Astra’s nature, status, and safety measures remain undisclosed.

Why Europe Is Rethinking Its AI Partnerships And Looking Beyond Palantir

European nations are increasingly seeking alternatives to Palantir for military and intelligence systems amid sovereignty concerns and recent procurement moves.

One-click Employee Offboarding For Startups Without IT

A new offboarding workflow for startups without IT is being tested, promising automated revocation of access when employees leave. Details are emerging.