Minimal editorial cover: white background with a simple shield-and-bandage motif in muted red and gray, no large text

PHP Ships Emergency Patches for Two Critical 'PHP2Shell' RCE Flaws

PHP released emergency security updates for two unauthenticated remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619, each rated CVSS 9.2. Patches cover supported PHP 8.x branches; PHP 5 through 8.1 are vulnerable and will not be patched.

It was the kind of coordinated scramble the open-source world hasn’t rehearsed in a while. On Wednesday, October 21, the PHP security team shipped emergency patches for two critical remote code execution vulnerabilities, collectively tracked as PHP2Shell: CVE-2026-109618 and CVE-2026-109619, each carrying a CVSS v4.0 score of 9.2.

Both flaws allow unauthenticated remote code execution — no login required. According to BleepingComputer’s coverage, CVE-2026-109618 chains weaknesses to trigger out-of-memory corruption for code execution as the web worker account, while CVE-2026-109619 exploits stale global state to enable unauthenticated heap use-after-free, memory disclosure, and code execution with the web worker’s privileges. The flaws affect all PHP installations that serve web requests: PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed.

Patch now, or go dark

The release was scheduled for 14:00 UTC on October 21, with patches landing in PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12. PHP 5 through 8.1 are also vulnerable, but those branches are end of life and will not receive patches — a cold reality for the long tail of unmaintained deployments. VirusTotal estimates put more than 5.1 million PHP hosts exposed online, with roughly 3.8 million having at least one port open.

The response was unusually high-profile. The U.S. National Security Agency published an advisory urging critical patching, and CERT-EU issued its own security advisory (2026-018) advising organizations to isolate internet-facing applications from public networks where immediate patching isn’t feasible. Drupal’s security team posted a rare public service announcement telling site owners to reserve time for the update.

Some operators didn’t wait for the patch. Pieter Levels, the indie developer behind sites like Nomad List, wrote on X that he had pre-emptively disconnected all of his sites and VPS servers from the web ahead of the release, noting that “69.3% of the web runs on PHP so this is going to be intense.” Hours later, after Ubuntu published its backported fix, he reported everything was back up — and praised the speed of the Ubuntu and PHP teams.

The part that should worry you

Datadog Security Labs independently reproduced the vulnerabilities and delivered the grimmest line of the day: application-level authentication cannot block an attack, because PHP processes the malicious request before any application code runs. Community-suggested mitigations, such as disabling session.upload_progress, do not protect you. Only patching fixes these flaws.

The timing also feeds a larger anxiety. Levels framed the incident as the start of a new era: “AI-assisted vulnerability exploits will now increasingly happen to any language, any framework, any server software… A new era of cybersecurity has begun.” He pointed to Node.js, which also patched a high-severity vulnerability this week. The context supports him: OpenAI is currently scaling its “Patch the Planet” program for global coordination as agents uncover critical vulnerabilities, and AI Weekly’s tracking lists an Anthropic report from October 20 on Claude flagging hundreds of security issues across open-source projects.

Machine-speed bug hunting means machine-speed disclosure windows, too. The PHP2Shell release was handled about as well as a coordinated disclosure can be — announced a day ahead, patched on schedule, backed by government advisories. But with millions of hosts exposed and unsupported PHP versions abandoned, the question is no longer whether the next such scramble will happen. It’s which language goes first.