CVE-2026-129289 puts some WordPress PHP servers at risk
CVE-2026-129289 is a critical PHP-FPM vulnerability that can enable unauthenticated code execution on some WordPress servers. PHP published the advisory on November 19, 2026, after fixed releases appeared on November 18 and 19. The flaw has a CVSS v4.0 severity score of 9.2 out of 10. It is a PHP vulnerability, not a defect in WordPress Core, a plugin, or a theme, and updating WordPress does not update PHP.
PHP-FPM is the service that runs PHP code for a website. The vulnerability affects servers where PHP-FPM is vulnerable and the web server reuses its private connections to that service. An attacker who knows the path to an existing PHP file may be able to make PHP process a second request that bypassed the web server's normal routing and access checks. Successful exploitation can run PHP code with the permissions of the website's PHP process.
The attack works because PHP can leave part of a request unread. If a web server keeps the connection open and reuses it, PHP may interpret those leftover bytes as a new request. The technique does not require memory corruption, guessing a memory address, or winning a timing race. PHP's advisory also identifies Apache mod_proxy_fcgi with enablereuse=on as an affected configuration. Wordfence testing covered NGINX, not Apache.
Standard NGINX configurations do not enable this connection reuse by default. NGINX documents fastcgi_keep_conn off as the default. However, WordOps, a server-management tool for WordPress, currently enables fastcgi_keep_conn on and defines cached PHP-FPM connections in its NGINX templates, making this a real production configuration rather than only a laboratory possibility.
WordPress matters because the attack needs an application to open php://input, the stream representing an incoming request body, while affected bytes remain unread. Normal REST requests, which are requests made through WordPress's standard interface for structured web operations, call WP_REST_Server::serve_request(), which uses WP_REST_Server::get_raw_data() to read php://input. In the tested path, a specially formed request body made PHP stop parsing early, leaving crafted bytes on the reused connection when WordPress reached this code.
The demonstrated route used stock WordPress Core and did not require a vulnerable plugin or theme, a WordPress account, an existing session, or attacker-created content. It still required both a vulnerable PHP-FPM release and connection reuse between the web server and PHP. The Wordfence Threat Response team reproduced unauthenticated PHP code execution through a stock WordPress 7.1.5 REST request in an isolated lab. The target used PHP 8.2.35 behind NGINX with PHP-FPM connection reuse enabled. The same request did not execute code on PHP 8.2.36 or when connection reuse was disabled.
The first fixed releases for supported branches are PHP 8.2.36, 8.3.37, 8.4.28, and 8.5.13. PHP says the vulnerable code dates back to PHP 5.6.0, so PHP 5.6 through 8.1, which are unsupported branches, may also be affected and have no fixed release. Sites on those branches should move to a supported branch.
Linux distributions and hosting providers may backport the fix without changing the first three version numbers. Owners using managed or shared hosting should check the provider's security notices, status page, dashboard, or customer communications. Administrators of self-managed servers should check the complete package revision and the vendor's security notice, install the fixed package, and restart or redeploy the affected service. The PHP-FPM version serving the website is the important one, because command-line PHP can use a different version. WordPress Site Health can report the web process's PHP version, but cannot confirm a backported fix or prove that every affected PHP process was restarted.
PHP disclosed six other critical vulnerabilities in the same November security-release cycle. CVE-2026-129496 can cause a timezone cache memory error after a particular startup diagnostic is written through PHP's file-based error log and followed by an early diagnostic in a fresh PHP worker. Remote PHP-FPM worker crashes were demonstrated, while published code-execution tests required known process memory addresses and additional server settings, so it is not a confirmed general WordPress takeover path.
CVE-2026-126714 involves partly overwritten session files. It needs file-based PHP sessions, attacker influence over session data, an interrupted write, a later read, and suitable application code. WordPress Core does not use native PHP sessions, but plugins, themes, custom code, or another application can add them. CVE-2026-115560 involves a session format mismatch connected to PHP's upload-progress feature. Stock WordPress does not normally create the required PHP session, although shared session storage between applications can make the issue relevant.
CVE-2026-129481 involves an interrupted session shutdown. Application code must fail during session cleanup, followed by another request reaching the same PHP process. PHP confirmed a memory error and crashes, but did not demonstrate code execution through this path. CVE-2026-129474 and CVE-2026-129182 involve fatal-error backtrace memory errors. Their documented conditions include PHP 8.5, particular error-reporting or server settings, and application behavior. The demonstrated CVE-2026-129474 attack is blocked by PHP's standard php.ini-production configuration, and code execution was not shown for the CVE-2026-129182 path.
The fixed release for each PHP branch addresses every listed issue affecting that branch. As of November 20, 2026, CVE-2026-129289 was not listed in CISA's Known Exploited Vulnerabilities catalog, but public technical details are available. Site owners should therefore not wait for evidence of exploitation before updating.
If an update cannot be installed immediately, disabling PHP-FPM connection reuse at the web server blocks the demonstrated CVE-2026-129289 path, but does not fix the other PHP vulnerabilities. Container users need to rebuild and redeploy from a fixed PHP base image, because restarting an old container does not replace its vulnerable files. After updating, check the website, REST API, scheduled tasks, and important plugin functions, and verify the PHP-FPM version actually serving the site. Keep WordPress, plugins, themes, and Wordfence current as well, while remembering that none of those updates replaces the PHP update.
AEU Hosting provides managed WordPress hosting, secured end to end, which is directly relevant for site owners who do not manage PHP and PHP-FPM themselves. Regardless of hosting model, the immediate priority is to install the fixed PHP release or vendor package, restart or redeploy the affected services, and confirm which PHP-FPM version serves the website.