PHP’s November 2026 Security Release: What Reaches WordPress
Our summary
PHP's security team shipped versions 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November 2026, closing 18 vulnerabilities, seven of them rated Critical with a CVSS of 9.2. None of these bugs live inside WordPress itself — they sit in the PHP runtime underneath it — so updating plugins or core offers no protection; only upgrading the PHP binary does.
Patchstack's analysis singles out two issues as genuinely concerning for ordinary WordPress hosting. CVE-2026-129496, a timezone-cache use-after-free, needs nothing from the application and can be triggered by a routine startup diagnostic combined with a file-based error log, making it reachable on configurations many sites drift into. CVE-2026-129289 enables PHP-FPM request smuggling through unread php://input data, a condition WordPress satisfies on every REST and XML-RPC request; whether it's exploitable depends solely on whether the front-end server reuses FastCGI connections. The remaining bugs — covering sessions, HTTP stream wrappers, SOAP, DOM, PHAR and PHP-CGI — require rarer setups or already-compromised workers to reach.
Administrators should move immediately to the patched branch matching their version (8.5.13, 8.4.28, 8.3.37 or 8.2.36), since PHP 8.1 and older are end of life and remain permanently exposed. Until the update lands, disabling FastCGI connection reuse and turning off session.upload_progress.enabled are the highest-value stopgaps.
Below is the opening; the full story is at Patchstack.
From Patchstack
PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 came out on 19 November 2026. Together they fix 18 CVEs, seven of which are rated Critical at CVSS 9.2. The pre-announcement a day earlier said the critical issues “require either non-default configuration or uncommon setups”.
That holds for most of them. It holds less well for two, which are reachable on setups that are ordinary on WordPress hosting, and a third was switched on by default in every PHP build until this release.…
Worried this affects your company?
Discuss a security assessment of your internet-facing systems. Scope agreed before testing.