On this page (7 sections)

PHP published advisories for several critical vulnerabilities on November 19, 2026, with fixed PHP releases published on November 18 and 19, according to Wordfence. One of them, CVE-2026-129289, is a request smuggling flaw in PHP-FPM that, per its CVE record, can let an unauthenticated remote attacker run PHP code, but only on servers with a specific configuration.

If you run WordPress or any other PHP site on your own server, VPS or managed hosting where you control the web server settings, check your PHP version and your FastCGI connection settings today.

What happened

The CVE record for CVE-2026-129289, published on 2026-11-19, describes a flaw in how PHP cleans up at the end of a request. If an application opens the php://input stream but does not read the request body to the end, PHP does not discard the unread remainder when the request shuts down. The record also lists a GitHub advisory in the php-src repository as a reference; the research did not include that page's content, so this article relies on the CVE record text.

Under certain conditions, the record says, PHP-FPM then parses those leftover bytes as a new FastCGI request. A single crafted multipart/form-data request can forge a backend request with attacker-chosen parameters such as SCRIPT_FILENAME, REMOTE_ADDR and PHP_ADMIN_VALUE, which can lead to execution of attacker-controlled PHP code.

The Wordfence post is the only independent coverage found so far, and the research available to us contains only its summary. It says PHP published advisories for several critical vulnerabilities, but we have no details or identifiers for the others, so this article does not describe them. Check the official PHP advisories for the full list.

Why the configuration matters

Request smuggling happens when two systems disagree about where one request ends and the next begins. Here, the web server and PHP-FPM end up disagreeing about leftover body bytes.

According to the CVE record, the PHP-FPM attack path applies when the front end reuses backend connections, which is not the default in nginx or Apache. The examples it gives are nginx with fastcgi_keep_conn on, or Apache mod_proxy_fcgi with enablereuse=on. Our own reading, not a statement from the record: when connections are not reused, there is presumably no later request on the same connection for the leftover bytes to attach to, which would explain why the default setups are not described as affected.

For LSAPI, the record says subsequent requests on the connection can be disrupted.

Who is exposed

  • Servers running PHP-FPM with nginx fastcgi_keep_conn on, or Apache mod_proxy_fcgi with enablereuse=on.
  • Any site on an affected PHP branch: before 8.2.36, 8.3.37, 8.4.28 or 8.5.13 on the matching branch.
  • Sites where application code opens php://input and may not read it fully. The record describes this as the trigger condition; it does not say which WordPress plugins or themes do this, and we cannot confirm that for any specific one.

Shared hosting customers usually cannot change these settings and depend on the host to update PHP. If that is you, ask your host which PHP build you are on and when the fixed release will be applied.

How to check your exposure

First, find your PHP version. This read-only command prints the installed CLI version. The CLI and PHP-FPM can differ on servers with several PHP versions, so also check the FPM version your site uses.

Print the PHP CLI version (any Linux server)Shell
php -v

Next, look for connection reuse in your web server configuration. These grep commands only read files and show lines that mention the settings named in the CVE record. The paths are common defaults and may differ on your system.

Search nginx configuration for fastcgi_keep_conn (look for 'on')Shell
grep -R "fastcgi_keep_conn" /etc/nginx/
Search Apache configuration for enablereuse (look for 'on')Shell
grep -Ri "enablereuse" /etc/apache2/ /etc/httpd/ 2>/dev/null

No match means the setting is not set explicitly, so the default applies, which the record says is not connection reuse. A match showing on, combined with an unpatched PHP version, is the combination to fix first.

What to do now

  1. Identify the PHP version used by PHP-FPM for each site, not just the CLI version.
  2. Update PHP to 8.2.36, 8.3.37, 8.4.28 or 8.5.13 (or later) on your branch, using your distribution's package manager or your host's control panel.
  3. Restart PHP-FPM after the update so the running service uses the new binary.
  4. If you cannot patch immediately, check whether fastcgi_keep_conn or enablereuse is turned on and consider turning it off until you update. This is our inference from the trigger condition in the CVE record, not an official workaround, so test it first.
  5. Take a backup and test your site after the update, especially if you run older plugins or themes.
  6. If you run a PHP branch older than 8.2, note that the record lists fixes only for 8.2 to 8.5 and does not describe older branches. Check the official PHP advisory for your branch.
  7. As a general precaution, skim web server and PHP logs for unusual multipart/form-data POST requests from before you patched. The research gives no known indicators, so treat this as a loose sanity check.
Caution. Restarting PHP-FPM or the web server briefly interrupts requests. Do it in a maintenance window and validate the web server configuration before reloading.

On Debian or Ubuntu, this read-only command lists installed PHP packages and their versions, which helps confirm the result after an update. Package names depend on your repository and PHP branch.

List installed PHP packages with versions (Debian/Ubuntu)Shell
dpkg -l | grep -i php

On RHEL, Fedora and similar systems, this read-only command does the same.

List installed PHP packages with versions (RHEL/Fedora family)Shell
rpm -qa | grep -i php

Distributions often backport fixes without changing the upstream version number, so a version string like 8.3.36 on a distribution package may already include the fix. Check your distribution's tracker for the status of your release, such as the Ubuntu CVE page or the SUSE bug entry, both listed as references for this CVE.

The CVE record also lists a GitHub issue in the anonaddy/docker project as a reference. We did not review its content, so we cannot say how it relates to your setup. If you build containers, check which PHP version your base image provides.

Detection and monitoring afterwards

The research does not describe indicators of compromise for this flaw, so there is no reliable signature to hunt for. Practical steps are general ones: watch for new or modified PHP files in upload and plugin directories, unexpected admin users, and unusual outbound connections from the web server. Our guide on how to check if a website is hacked walks through the basics, and what to do if your website is hacked covers response.

A site-wide malware scan can help spot injected code after the fact, though it cannot prove a server was never abused. See what outside-in malware detection can and cannot see, and keep the WordPress security checklist handy for general hardening. A web application firewall can add a layer of filtering, but updating PHP is the actual fix here.

Timeline

Key dates from the sources
DateEvent
2026-11-18 and 2026-11-19Fixed PHP releases published (per Wordfence)
2026-11-19PHP advisories published (per Wordfence); CVE-2026-129289 record published
2026-11-20Date of the Wordfence post covering these PHP vulnerabilities

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-129289 and Other Critical PHP Vulnerabilities: What WordPress Site Owners Need to Knowwordfence.com ·
  • PHP
  • PHP-FPM
  • WordPress
  • CVE-2026-129289
  • request smuggling