PHP security update fixes 18 CVEs, two affect 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. Seven vulnerabilities are rated Critical at CVSS 9.2, a score used to describe the seriousness of a security flaw. PHP’s pre-announcement said the critical issues required a non-default configuration or uncommon setup. Patchstack’s analysis found that description fits most of the release, but two vulnerabilities are reachable in configurations commonly found on WordPress hosting, while a third feature was enabled by default in every PHP build until this release.
These are PHP and hosting-level vulnerabilities, not WordPress bugs. Updating WordPress does not fix them. The most important issue is CVE-2026-129496, a timezone cache use-after-free. A use-after-free happens when software continues using memory after it has been released. The issue does not depend on an application using dates. It can be triggered by a startup diagnostic, such as a warning caused by a large form, when PHP uses a file-based error log and has a relevant timezone configuration. Patchstack researchers crashed an FPM worker on default settings and demonstrated code execution under both PHP-FPM, the process manager commonly used to run PHP websites, and mod_php, with ASLR enabled. No application-level change can prevent it because the application is not involved.
The other issue that deserves immediate attention is CVE-2026-129289, a PHP-FPM request-smuggling flaw. Request smuggling means that data intended for one request can be interpreted as another request. It requires the front end to reuse FastCGI connections, the connections used between a web server and PHP, and an application that opens php://input without draining it. WordPress meets that application condition on every REST request, because its REST interface reads the raw request body. The same behaviour is present in xmlrpc.php and the bundled IXR server. With a malformed multipart request, leftover data can be parsed as a new FastCGI request, potentially allowing attacker-controlled PHP to run as the worker user, bypassing front-end routing and spoofing client addresses. Until PHP is updated, the relevant interim measure is to disable connection reuse.
Two session vulnerabilities, CVE-2026-126714 and CVE-2026-115560, are narrower but worth understanding. PHP can write session files during multipart upload processing before an application asks to start a session. An unauthenticated visitor can submit PHPSESSID and PHP_SESSION_UPLOAD_PROGRESS fields to make PHP write a session file using an ID they chose. The setting session.upload_progress.enabled was enabled by default in PHP 8.4.27 and changed to disabled in 8.4.28. Writing a file alone does not complete the attack: software must later read it with PHP’s serializer, and plugins that call session_start() are uncommon. Risk increases when separate tenants share a session.save_path, because separate FPM pools do not automatically create separate session storage.
The remaining fixes depend on more specialised conditions. CVE-2026-129474 affects PHP 8.5 and involves magic methods such as __call or __callStatic during fatal-error backtrace creation. It requires zend.exception_ignore_args=0 and fatal_error_backtraces=1. The production PHP configuration blocks the combination, although pool overrides and .user.ini files should still be checked. WordPress core defines those magic methods in only 14 places. CVE-2026-129291, a PHP-FPM epoll use-after-free, matters after code execution has already been achieved inside a worker and can turn it into execution as the FPM master, usually root. It requires catch_workers_output, which is enabled in the official PHP-FPM Docker images but is not the PHP default.
PHP’s HTTP stream wrappers, built-in functions for fetching remote content, contain two other issues. CVE-2026-128064 can send an HTTPS:// URL in plaintext because the check for the secure scheme is case-sensitive. CVE-2026-127960 can cause quadratic processing of folded HTTP response headers and occupy workers with malicious responses. WordPress core does not reach these paths: its HTTP transports use cURL and WP_Http_Streams, while the latter opens a socket directly, and feeds use wp_safe_remote_request(). Plugins that call file_get_contents() or fopen() on remote URLs remain the relevant exposure.
The other vulnerabilities are mainly plugin or specialised deployment territory. The SOAP fixes require ext-soap to parse untrusted SOAP or XML. The PHAR signature bypass requires an attacker to rewrite an OpenSSL-signed Phar and is more relevant to tooling. The DOM double free affects the Dom\\XMLDocument and Dom\\HTMLDocument APIs introduced in PHP 8.4, while WordPress uses the legacy DOMDocument class. PHP-CGI, cgi.fix_pathinfo, the PHP-FPM status endpoint, and a URI of roughly 2 GiB are required for other fixes. WordPress core does not use SoapClient or load signed Phars at runtime.
PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36 should be installed according to the branch in use. PHP 8.1 and earlier are end of life and received none of these fixes. If an immediate update is not possible, 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 unnecessary, verify zend.exception_ignore_args=On on PHP 8.5, and give each tenant a separate session.save_path. Plugins should also be audited for remote URL fetching with file_get_contents(), SOAP use and session_start().
The PHP security update followed a 18 November pre-announcement. Seventeen fixes have GitHub Security Advisories in php/php-src, while the eighteenth came from the bundled uriparser upgrade to version 1.0.3. A managed WordPress environment such as AEU Hosting, which provides managed WordPress hosting secured end to end, is relevant for organisations that need hosting operations kept within a security-focused managed service, but the PHP version still needs to be confirmed and updated for the site’s branch.