PHP security update fixes 18 CVEs, two affect WordPress hosting
The PHP security update released on 19 November 2026 fixes 18 CVEs in PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. PHP is the server-side programming language WordPress runs on. Seven of the fixes are rated Critical at CVSS 9.2, although the PHP security team said before release that the critical issues required non-default configuration or uncommon setups.
Patchstack’s analysis found that description fits most of the release, but not all of it. Two vulnerabilities can be reachable on configurations seen in ordinary WordPress hosting, while a third feature was enabled by default in every PHP build until this release. These are not WordPress vulnerabilities, so updating WordPress or its plugins does not fix them. The required update must happen at the hosting or server level.
The two issues that deserve priority are the timezone cache use-after-free, CVE-2026-129496, and PHP-FPM request smuggling, CVE-2026-129289. A use-after-free is a memory error in which software continues using memory after it has been released. The timezone issue affects PHP 8.2, 8.3, 8.4 and 8.5, and can be triggered by a startup diagnostic written to a file-based error log. Patchstack says the trigger can be an invalid date.timezone setting or a deprecation notice, followed by an early warning such as the max_input_vars warning caused by a large form. Researchers crashed an FPM worker on default settings and demonstrated code execution under both FPM and mod_php with ASLR enabled. The application does not need to participate.
The PHP-FPM request smuggling issue affects all four branches and requires FastCGI connection reuse, a setting that allows a front end to reuse connections to PHP-FPM, through fastcgi_keep_conn in nginx or enablereuse in mod_proxy_fcgi. It also requires the application to open php://input without draining it. WordPress meets that application condition on every REST request because WP_REST_Server::serve_request() reads raw request data, including multipart requests. xmlrpc.php and the bundled IXR server do the same. A malformed multipart body can leave data that is parsed as another FastCGI request, potentially allowing attacker-controlled PHP to run as the worker user, bypass front-end routing and spoof client addresses. Until PHP is patched, the advisory recommends disabling connection reuse. Simply reading to the end is not a reliable control.
Two session vulnerabilities, CVE-2026-126714 and CVE-2026-115560, are less likely but reveal an important hosting detail. PHP can write session files during multipart parsing before the application starts, when a visitor supplies PHPSESSID and PHP_SESSION_UPLOAD_PROGRESS fields. session.upload_progress.enabled was set to 1 in PHP 8.4.27 and changed to 0 in 8.4.28. The feature had remained enabled by default since it was introduced in PHP 5.4.0. Exploitation still requires something to read the file with PHP’s serializer, such as a plugin calling session_start(), and a suitable gadget chain. Shared session.save_path values are a concern because separate FPM pools do not automatically receive separate session storage, allowing one tenant’s planted records to reach another.
The HTTP stream wrapper fixes are mainly plugin territory. CVE-2026-128064 can send an HTTPS:// URL in plaintext because the built-in wrapper checks for a lowercase s at a fixed position. CVE-2026-127960 can cause quadratic processing through folded HTTP response headers and exhaust workers. WordPress core uses cURL and WP_Http_Streams, with the latter opening a socket through stream_socket_client(), while feeds use wp_safe_remote_request(). Plugins that use file_get_contents() or fopen() on remote URLs instead of wp_remote_get() may still be exposed.
The remaining fixes are narrower. CVE-2026-129474 affects PHP 8.5 only and involves magic method backtraces, with remote code execution confirmed by the advisory under zend.exception_ignore_args=0 and fatal_error_backtraces=1. Production configuration normally sets the first option to On, while development configuration sets it Off. PHP core contains only 14 __call or __callStatic definitions, and display_errors=0 does not prevent the backtrace from being built. CVE-2026-129291 is a PHP-FPM epoll use-after-free that matters after code execution has already been achieved inside a worker. It requires catch_workers_output=yes, enabled in the official PHP-FPM Docker images but not by default in PHP itself.
The other issues affect components or configurations WordPress core does not normally reach. They include the PHAR OpenSSL signature bypass, CVE-2026-128090; PHP-CGI PATH_INFO out-of-bounds access, CVE-2026-129538; SOAP information disclosure, CVE-2026-15353; SOAP DTD entity reference use-after-free, CVE-2026-129506; the DOM XML double free, CVE-2026-129501; incorrect RFC 3986 URI serialization in PHP 8.5, CVE-2026-129438; and PHP-FPM status endpoint XSS, CVE-2026-129292. The affected conditions include signed PHAR files an attacker can rewrite, php-cgi with cgi.fix_pathinfo=1, ext-soap parsing untrusted content, the newer Dom\\XMLDocument or Dom\\HTMLDocument APIs, a URI of roughly 2 GiB, and a status endpoint rendered as HTML. The bundled uriparser dependency was also upgraded to 1.0.3 in PHP 8.5 under CVE-2026-48841.
The PHP security team pre-announced the release on 18 November 2026. On 19 November, it published PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. Seventeen fixes have GitHub Security Advisories against php/php-src, while the eighteenth came from the bundled uriparser upgrade. PHP 8.1 and earlier are end of life and received none of these fixes.
Site owners should move to the matching patched branch rather than wait for a WordPress maintenance window. If an immediate update is impossible, administrators should disable session.upload_progress.enabled administratively in every relevant pool and virtual host, turn off FastCGI connection reuse, clear startup diagnostics and restart the FPM master and workers, consider syslog instead of file logging, disable catch_workers_output where it is not needed, verify zend.exception_ignore_args=On on PHP 8.5 including pool overrides and .user.ini files, and give each tenant a separate session.save_path. Plugin audits should focus on remote URL access with file_get_contents(), SOAP use and session_start(). For site owners who do not manage PHP themselves, managed WordPress hosting such as AEU Hosting is relevant because it is secured end to end.