PHP security release fixes bugs that let a stranger run code on some PHP sites. Update to 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (CVE-2026-129289)

8 min read

How to fix CVE-2026-129289: upgrade PHP to 8.5.13, 8.4.28, 8.3.37 or 8.2.36. PHP's November 19 security release closes 17 advisories, including a PHP-FPM bug that lets a stranger run code on servers that reuse FastCGI connections. Here is the two-minute check.

BREAKING: PHP security release fixes bugs that let a stranger run code on some PHP sites. Update to 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (CVE-2026-129289)
On this page

PHP shipped security releases on November 19, 2026 that close bugs which, on some servers, let a stranger on the internet run their own code on a PHP website. PHP powers WordPress, Magento, Laravel apps and a large share of the web, so this one is worth a look today even though most sites are not in the worst-case setup. PHP's security team warned a day ahead that the top issues are rated critical, and that those critical issues need a non-default configuration or an uncommon setup.

The fix is one upgrade on whichever branch you run: PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36. This post is our operator read of the release: which bugs matter, how to tell in two minutes whether your server is in the risky setup, and what to change if you can't upgrade today.

How to fix

Upgrade PHP to the fixed release for your branch, then restart PHP-FPM (or Apache, if you run PHP as an Apache module) so the old workers go away:

php -v                      # CLI version
php-fpm -v                  # FPM version (the binary may be php-fpm8.3, php-fpm8.4, ...)
sudo systemctl restart php8.3-fpm   # use your FPM service name
  • PHP 8.5: 8.5.13 or later
  • PHP 8.4: 8.4.28 or later
  • PHP 8.3: 8.3.37 or later
  • PHP 8.2: 8.2.36 or later

PHP 8.1 and older got no release today. If you still run them, this is one more reason to move.

Check the CLI and the web server separately. They are often different builds, and the web one is the one that matters. A phpinfo() page or php-fpm -v tells you what the site actually runs.

When we checked at about 9:30 AM ET on November 19, the official php Docker image had no 8.5.13, 8.4.28, 8.3.37 or 8.2.36 tags yet, and Linux distribution packages usually land a few days after upstream. If you depend on either, use the workarounds below until the rebuilt image or package shows up.

The bug to check first: CVE-2026-129289

CVE-2026-129289 (GHSA-qc49-hpvq-g2w6, CVSS v4.0 9.2) is a request smuggling bug in PHP-FPM, the process most nginx and many Apache sites use to run PHP. It has been in PHP since 5.6.0.

In plain terms: when the web server keeps one connection open to PHP-FPM and reuses it for many visitors, PHP can forget to throw away the leftover part of a request body. An attacker can shape that leftover into a second, hidden request that the web server never saw or approved. That hidden request can switch on PHP settings that make PHP run code the attacker sent. The PHP advisory says this needs no password, no memory tricks and no unusual PHP setting, just one request.

Two things have to be true for that:

  1. The front end reuses FastCGI connections: fastcgi_keep_conn on; in nginx, enablereuse=on on Apache mod_proxy_fcgi, an HAProxy FastCGI backend that keeps connections, or LiteSpeed's LSAPI (where the advisory confirms broken requests but not code execution).
  2. The app opens the request body stream (php://input) and doesn't read it to the end. The advisory notes this happens in frameworks that create the input stream before routing or login checks, even on endpoints that never use the body.

The first condition is the one you can check fast. Both nginx and Apache leave connection reuse off by default, so a stock config is not exposed to the demonstrated attack:

nginx -T 2>/dev/null | grep -n fastcgi_keep_conn
grep -rn "enablereuse" /etc/apache2 /etc/httpd 2>/dev/null

If either prints an enabled line, treat that server as exposed until it runs the fixed PHP. If you can't upgrade today, turn reuse off (fastcgi_keep_conn off; or remove enablereuse=on), reload, and accept a little extra connection overhead. Never expose the PHP-FPM port itself to the internet.

The other bugs that can lead to code execution

These are serious on paper, but each one needs a specific setting or a specific app pattern. Here is how to tell if you have it.

  • CVE-2026-129474 (PHP 8.5 only): a memory bug when PHP builds an error backtrace while code goes through __call() or __callStatic(), which Laravel facades and many proxies use. The demonstrated attack needs zend.exception_ignore_args=0. The php.ini-production file sets it to 1, which blocks this path. PHP's advisory names Laravel facades and a Magento guest shipping endpoint as reachable code paths, but says full exploitation of a real Laravel or Magento install has not been shown. Workaround: set zend.exception_ignore_args=1 (or fatal_error_backtraces=0) in the FPM pool config and restart.
  • CVE-2026-115560: a session format mix-up that can unpack attacker data as PHP objects when session upload progress is on and two pieces of code read the same session with different serializers. This is the session bug we flagged on October 23 as still unpatched after the PHP2Shell emergency release. It is fixed now. The fix also turns session.upload_progress.enabled off by default and blocks changing the session serializer at runtime while upload progress is on. If an app relies on upload progress bars, test that after upgrading.
  • CVE-2026-126714: if a write to a session file is cut off halfway, the file can end up holding pieces of two sessions, which PHP may then unpack as attacker-controlled objects. It needs the attacker to influence session data, interrupt the write at the right moment, and an app with a usable object chain. It affects the default file-based session storage.
  • CVE-2026-129496: a memory bug in timezone handling that needs a warning during PHP startup (for example a bad date.timezone value or a deprecated session setting) plus errors logged to a file. Clean up startup warnings, or log to syslog, and this path closes.
  • CVE-2026-128090: an attacker who can change an OpenSSL-signed PHAR archive can switch it to a plain hash and PHP accepts it as signed. Only matters if you run signed PHAR files from a place someone else can write to.
  • CVE-2026-129291: someone who can already run PHP code in an FPM worker can become the FPM master process, which usually runs as root, when catch_workers_output = yes. This matters most on shared hosting.

To see the settings above on the PHP that serves your site, check the FPM pool files as well as the main php.ini, because pool overrides win:

php-fpm -i 2>/dev/null | grep -E 'zend.exception_ignore_args|fatal_error_backtraces|session.upload_progress.enabled|session.serialize_handler'
grep -rnE "catch_workers_output|exception_ignore_args|upload_progress" /etc/php/*/fpm/ 2>/dev/null

Who is not in scope

  • For CVE-2026-129289: sites where nginx or Apache opens a fresh connection to PHP-FPM for each request, which is the default for both. Sites that run PHP as an Apache module (mod_php) don't use FastCGI at all.
  • The PHP-CGI bug in this release (CVE-2026-129538) only hits php-cgi with particular web server path mappings. PHP-FPM and mod_php are not affected. PHP rates it moderate: a crash or memory leak, with code execution claimed but not confirmed.
  • PHP 8.2, 8.3 and 8.4 are not affected by CVE-2026-129474. That one is 8.5 only.
  • Managed hosting where the host runs PHP for you. They have to upgrade it. Check their status page or ask.

What this is not

It is not a known attack. PHP reports no exploitation, none of these CVEs are on CISA's Known Exploited Vulnerabilities catalog as of this writing, and there is no public exploit code. It is also not another PHP2Shell, the October emergency release whose bugs landed on CISA's exploited list within days. This release is a scheduled one, and the worst bugs need a setting or an app pattern most sites don't have. Patch it this week, and today if the fastcgi_keep_conn check above prints a line.

The rest of the release

The same upgrade fixes lower-severity bugs too: a crash and possible memory leak in the SOAP extension when it reads untrusted XML (CVE-2026-129506 and CVE-2026-15353), an XSS on the PHP-FPM status page (CVE-2026-129292), HTTPS and FTPS URLs written in mixed case going out unencrypted (CVE-2026-128064), a denial of service from folded HTTP response headers (CVE-2026-127960), a use-after-free after interrupted session shutdown (CVE-2026-129481), a double free in the new DOM XML serializer (CVE-2026-129501, PHP 8.4 and 8.5), and on PHP 8.5 a second backtrace memory bug (CVE-2026-129182) and a URI serialization bug (CVE-2026-129438). PHP 8.5.13 lists 17 advisories in total, 8.4.28 lists 14, 8.3.37 lists 13 and 8.2.36 lists 12.

What do people ask about the November 2026 PHP security release?

Is my WordPress or Laravel site affected?

It runs on affected PHP if PHP is older than 8.5.13, 8.4.28, 8.3.37 or 8.2.36. Whether the worst bugs can be used against it depends on server settings, mainly whether nginx or Apache reuses connections to PHP-FPM. Run the fastcgi_keep_conn and enablereuse checks above, then upgrade either way.

Is CVE-2026-129289 being exploited?

Not as of November 19, 2026. PHP reports no exploitation and there is no public exploit.

Can I fix CVE-2026-129289 without upgrading PHP?

You can block the demonstrated attack by turning off FastCGI connection reuse in nginx or Apache. That is a stopgap. Upgrade PHP to close it and the other bugs.

Why did my upload progress bar stop working after the update?

The fix for CVE-2026-115560 turns session.upload_progress.enabled off by default. If you need it, turn it back on explicitly and make sure every app and pool sharing that session storage uses the same session.serialize_handler.

If AI coding agents can run commands or install packages on your servers, scan your agent setup with HOL Guard (free) so a bad install or a risky config change gets stopped before it runs. Every advisory we track is in the HOL Guard CVE index.

References

All articles

Keep exploring

The engineering desk continues across the ecosystem: security research on shipping agents safely, and plugins that put the standards to work.