Egidio
Case file · October 23, 2026

PHP2Shell: two critical flaws in the language behind a large part of the web

On 21 October 2026, the PHP team released emergency fixes for two flaws rated 9.2 out of 10. On an unpatched server, a single request can be enough to run code without any account. There is nothing to install on your phone: the risk lies with the websites you use, and with what will come out of them in the weeks ahead.

✅ Confirmed by the vendor. Both flaws are described by the PHP security team itself (php.net announcement, GHSA-w8hw-w9fx-j79w, GHSA-6wmf-4rv5-p3rp). This case file sticks to what they establish.

What is established

9.2 / 10
Severity score (CVSS v4) given by the PHP team to each flaw. Early reports said 10; the official figure is 9.2.
Advisory GHSA-w8hw-w9fx-j79w, 21/10/2026.
0 accounts
No authentication is needed: the attack uses an ordinary web request, before the site even runs its own code.
php.net, 21/10/2026.
4 versions
Fixed versions: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older no longer receive official updates; minimal self-build fixes exist for 7.4, 8.0 and 8.1.
php.net, 21/10/2026.
5 modes
Affected server modes: PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. The risk is rated highest with mod_php, where code execution was validated with the default configuration.
php.net ; GHSA-w8hw-w9fx-j79w.

The two flaws, without jargon

🧠CVE-2026-109618 — running out of memory at the wrong moment

When a request exhausts its memory allowance, PHP stops while some internal data is only half prepared. The clean-up that follows still treats it as valid. An attacker who deliberately triggers this shortage, for example with a crafted form upload, can turn it into running their own code.

GHSA-w8hw-w9fx-j79w, “RCE via OOM corruption”.

♻️CVE-2026-109619 — leftovers from the previous request

A PHP server reuses the same process for several visitors. After a fatal error, data from one request can survive while the memory holding it has been freed; the next request can then use it. The file-upload progress feature, enabled by default, is a confirmed attack path.

GHSA-6wmf-4rv5-p3rp, “RCE via stale global state”.

Timeline

REPORTED
Before 21 October 2026
Details of the flaws circulate before the planned release date, under the name “PHP2Shell”. The PHP team brings the release forward and shares fixes in advance with Linux distributions and long-term support vendors.
CONFIRMED
21 October 2026
Release of PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 and of the two security advisories. The Canadian Centre for Cyber Security publishes alert AL26-026 the same day.
ONGOING
21–22 October 2026
Cloudflare deploys protection rules for all customers and says it has “observed attack traffic” targeting them. Rapid7 says it has not observed successful exploitation in the wild, but reports attempts and several public proofs of concept that only work in specific configurations.

What it means for you, if you run no server

🛒Websites that are slow to update become targets

A server flaw steals nothing directly from your phone. It does, however, open the customer databases of sites that do not patch in time: shops, charities, small booking sites. Data breaches announced in the coming weeks may be the result.

Egidio analysis, based on the php.net and Rapid7 advisories.

✉️Beware of messages riding on the news

After every high-profile flaw, messages pose as a host, a provider or a technical service: “update urgently”, “your site is compromised, click here”. A real provider never asks for a password or a payment by message. Always check by logging in to your usual account yourself.

Egidio analysis.
🛠️ Do you run a PHP website? Install the fixed version for your branch (8.5.12, 8.4.27, 8.3.36 or 8.2.35), or ask your host whether they have, then restart the PHP processes. The PHP team states that the workarounds (memory limit, disabling upload progress) do not make an installation safe: only the update fixes it. Updating WordPress or its plugins is not enough — PHP itself must be updated.

Frequently asked questions

Do I need to do anything on my phone?

No. The flaws affect web servers, not phones. The risk to you is indirect: a leak of your data from a poorly updated site, and fraudulent messages exploiting the news.

Are the flaws being exploited?

Cloudflare says it has observed attack traffic. Rapid7 had not observed successful exploitation in the wild as of 22 October 2026, but reports attempts and several public proofs of concept.

Which PHP versions should be installed?

PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 depending on the branch. PHP 8.1 and older no longer receive official updates; minimal fixes exist for 7.4, 8.0 and 8.1.

📌 Last checked: October 23, 2026. This case file will be updated if large-scale exploitation or a data breach linked to these flaws is established. Verifiable correction: contact@egidio.app.

Related reading

Cite this page Egidio — Threat Laboratory, « PHP2Shell: two critical PHP vulnerabilities, patched on 21 October 2026 », egidio.app/en/laboratoire/php2shell-critical-php-vulnerabilities-october-2026/. CC BY 4.0.

Free to reuse, including commercially, with attribution. Reuse terms.

Sources. PHP security team: announcement of 21/10/2026, advisory GHSA-w8hw-w9fx-j79w (CVE-2026-109618), advisory GHSA-6wmf-4rv5-p3rp (CVE-2026-109619) — primary sources. Canadian Centre for Cyber Security, alert AL26-026, 21/10/2026. Cloudflare, post of 21/10/2026 updated 22/10. Rapid7, 21/10/2026 updated 22/10.