CVE-2026-129289 puts PHP-FPM WordPress sites 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 issue does not affect every WordPress site, but site owners should update PHP without waiting to confirm whether their exact server configuration is exposed.
PHP-FPM is the service that runs PHP code for a website. The vulnerability received a CVSS v4.0 score of 9.2 out of 10. On an affected server, an attacker who knows the path to an existing PHP file may be able to make PHP run code with the permissions of the website’s PHP process, without logging in. This is a PHP vulnerability, not a defect in WordPress Core, a plugin, or a theme. Updating WordPress does not update PHP.
The attack depends on two conditions. The server must run a vulnerable PHP release, and the web server must reuse its private connections to PHP-FPM. Normally, a web server such as NGINX checks an incoming request before passing it to PHP-FPM. CVE-2026-129289 can make PHP leave part of a request unread. If that private connection remains open and is reused, PHP may interpret the leftover bytes as a second request. That second request bypasses the web server’s normal routing and access checks. The attack does not require memory corruption, a guessed memory address, or a timing race.
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. PHP also identifies Apache `mod_proxy_fcgi` with `enablereuse=on` as an affected configuration. Wordfence’s testing covered NGINX, not Apache.
WordPress matters because the documented attack requires the application to open `php://input`, which contains the incoming request body while affected bytes remain unread. Normal WordPress REST API requests, a way for software to communicate with WordPress, call `WP_REST_Server::serve_request()`, which uses `WP_REST_Server::get_raw_data()` to read that 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 Wordfence Threat Response team reproduced unauthenticated PHP code execution through a stock WordPress 7.1.5 REST request in an isolated laboratory. The target used PHP 8.2.35 behind NGINX with PHP-FPM connection reuse enabled. The same request did not execute code against an otherwise matched PHP 8.2.36 target, or when connection reuse was disabled. The demonstrated route required no vulnerable plugin or theme, WordPress account, existing session, or attacker-created content. It did require both the vulnerable PHP-FPM release and connection reuse.
The first fixed releases for supported PHP branches are PHP 8.2.36, 8.3.37, 8.4.28, and 8.5.13. PHP 5.6.0 through the 8.1.x branches have no fixed release because they are unsupported, so sites using them must move to a supported branch. Linux distributions and hosting vendors may backport a fix, meaning they apply the security change while keeping different package version numbers. Site owners should check the PHP-FPM version serving the website, not only the command-line PHP version. WordPress Site Health can report the web process’s PHP version, but it cannot confirm a backported fix or prove that every PHP process was restarted.
PHP disclosed six other critical vulnerabilities in the same November security-release cycle. CVE-2026-129496 can cause remote PHP-FPM worker crashes through a particular startup diagnostic written to PHP’s file-based error log, followed by an early diagnostic in a fresh worker. Published code-execution tests required knowledge of process memory addresses and additional server settings, so it is not a confirmed general WordPress takeover route.
CVE-2026-126714 concerns partly overwritten session files. It requires 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, although plugins, themes, custom code, or another application can add them. CVE-2026-115560 involves a mismatch between session formats when PHP’s upload-progress feature writes a session and another operation reads the same session ID and storage. It is narrow, but can matter when applications share PHP session storage. Stock WordPress does not normally create the required PHP session.
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 specific path. CVE-2026-129474 and CVE-2026-129182 involve fatal-error backtrace memory errors. Their relevance depends on 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.
As of November 20, 2026, CVE-2026-129289 was not listed in CISA’s Known Exploited Vulnerabilities catalog. Public technical details are available, however, so the absence of a catalog entry is not a reason to delay patching. The fixed release for each PHP branch addresses every listed issue affecting that branch.
On managed or shared hosting, check the provider’s security notices, status page, dashboard, or customer communications and follow its instructions. On a self-managed server, install PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, a later supported release, or the vendor’s fixed package, then restart PHP-FPM and any web-server processes that retain private connections. For containers, rebuild and redeploy from a fixed PHP base image, since restarting an old container does not replace its vulnerable files.
If an update is not immediately available, disabling PHP-FPM connection reuse at the web server blocks the demonstrated CVE-2026-129289 path, but it does not fix the other PHP vulnerabilities. After updating, confirm that the website, REST API, scheduled tasks, and important plugin functions still work, and verify the PHP-FPM version actually serving the site. Keep WordPress, plugins, themes, and Wordfence current as well. A managed service such as AEU Hosting is relevant for readers who want managed WordPress hosting secured end to end, while the PHP update itself still needs to follow the host’s specific guidance.
CVE-2026-129289 is therefore a credible unauthenticated threat when the vulnerable PHP-FPM version and connection-reuse settings coexist.