Two critical PHP core RCE flaws (CVE-2026-109618, CVE-2026-109619): emergency patches due Oct 21
On October 20, 2026, the PHP security team pre-announced two critical vulnerabilities after details leaked ahead of the embargo. Both are remote code execution flaws. PHP rates each 9.2 under CVSS v4.0, while researchers at watchTowr, who reproduced one of the flaws, rate both at 10.0 and describe them as affecting PHP versions 5 through 8. Full details, affected versions, and fixed versions are being withheld until the release.
Emergency security updates are scheduled for October 21, 2026 at 14:00 UTC (7:00 AM Pacific). The PHP team says it may release even earlier if details become public or active exploitation appears. PHP versions that have reached end of life, meaning anything older than PHP 8.2, will not receive patches.
No exploitation in the wild has been reported as of this writing, but the early leak means attackers may get a head start on reverse engineering the fixes once they land. PHP sits underneath WordPress and most shared hosting, so nearly every WordPress site is in scope until the patch is applied.
What to do
- Check your PHP version now (in WordPress: Tools, Site Health, Info, Server) and take a fresh backup before the release lands.
- Plan to apply the PHP update on October 21 as soon as your host publishes the fixed packages. If your host manages PHP, ask them when they will apply it.
- If you run PHP 8.1 or older, treat this as a forcing function: those branches get no fix, so test a newer PHP on staging and plan the upgrade.
Server-level flaws like this are why ZeroBreach starts with the server: recurring scans flag end-of-life runtimes, and the audit inventory shows exactly which PHP version every app is running before the emergency lands.