Two critical remote code execution bugs in PHP itself leaked before the emergency patch shipped.

CVE-2026-109618 and CVE-2026-109619, CVSS v4.0 9.2 each.

What happened:

On Oct 20 the PHP security team pre-announced an emergency release for Wednesday Oct 21, 2026 at 14:00 UTC. Per Sansec, the embargo broke the same day: watchTowr confirmed both flaws are RCE and a screenshot of an exploit tool leaked.

Why it matters:

PHP runs about 69% of websites with a known server-side language (W3Techs), including WordPress, Magento and Laravel sites. Sansec expects mass attacks within 15 minutes of the release. Sansec and GoDaddy report that PHP 8.1 and older will get no official fix, so only 8.2 and later are covered.

Status at publish time (Oct 21, 2026):

Release not yet shipped, fixed version numbers not yet published, not in CISA KEV, no confirmed in-the-wild exploitation.

What to do now:

1. Inventory every PHP version you run (servers, containers, shared hosting).
2. Tell your host or platform team to stand by for the 14:00 UTC release.
3. Patch the moment it drops. PHP core devs say patching is the only real fix.
4. Stopgap only: disabling session.upload_progress is an unofficial, partial mitigation suggested by Sansec. It is no guarantee and may break upload progress bars.
5. On 8.1 or older: plan a migration to 8.2+ now.

Sources:

PHP pre-announcement: https://www.php.net/archive/2026.php
Sansec research: https://sansec.io/research/php2shell
GoDaddy advisory: https://www.godaddy.com/resources/news/important-php-security-update-what-website-owners-need-to-do
PHP usage stats (W3Techs): https://w3techs.com/technologies/details/pl-php