On October 21, 2026, the PHP project released security updates for two critical vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619. PHP’s advisory says they can allow unauthenticated remote code execution: someone could run their own code on an unpatched web server without logging in.
PHP says every PHP installation serving web requests is at risk, and that only an update is a complete fix. PHP 8.1 and older no longer receive updates from the PHP project at all.
WordPress.org says the vulnerabilities are not specific to WordPress, and no WordPress update is required. What matters is the PHP version your server runs. In WordPress you can see it under Tools > Site Health > Info > Server, or ask your host.
- 2 critical vulnerabilities fixed
- CVE-2026-109618 and CVE-2026-109619
- 9.2 CVSS v4.0 score, each
- Rated critical in PHP’s advisories
- 8.2.35 or newer on PHP 8.2
- Fixed in 8.5.12, 8.4.27, 8.3.36 and 8.2.35
- 8.1 and older get no fix
- No longer updated by the PHP project
Sources, as of October 21, 2026: PHP security advisory, php.net, GHSA-w8hw-w9fx-j79w (CVE-2026-109618), GHSA-6wmf-4rv5-p3rp (CVE-2026-109619), NVD: CVE-2026-109618, NVD: CVE-2026-109619, WordPress.org: Critical PHP Security Release, PHP supported versions.