Blog / Security Advisories

PHP Security Release November 2026: PHP-FPM Request Smuggling, Session RCE, and How to Upgrade

On November 19, 2026, PHP released 8.5.13, 8.4.28, 8.3.37, and 8.2.36, fixing 17 CVEs across all supported branches. PHP rates the worst of them critical, but says they need non-default or uncommon setups. That makes this release different from October’s PHP2Shell: the question is not just “which version am I on?” but “which of these configurations do I run?” Here is how to answer that quickly, what to change if you cannot patch today, and how to upgrade.

· 11 min read

The headline bug is CVE-2026-129289, a CVSS 9.2 request smuggling flaw in PHP-FPM that has existed since PHP 5.6. If your web server reuses FastCGI connections, an attacker can hide a second request inside the body of the first and use it to run code. Alongside it are two session bugs that can lead to remote code execution, including CVE-2026-115560, which the October PHP2Shell fix left open, plus a PHP 8.5-only use-after-free, an FPM privilege escalation, and a PHAR signature bypass.

This article was created with AI assistance on release day. CVE and advisory IDs were checked against the official PHP 8.5.13 ChangeLog on php.net; preconditions and workarounds come from published advisory summaries. Full advisories were still being published, so confirm details on php.net and GitHub before acting.

TL;DR: what to install

BranchFixed releaseCVEs fixedSecurity support until
PHP 8.58.5.131731 Dec 2029
PHP 8.48.4.281431 Dec 2028
PHP 8.38.3.371331 Dec 2027
PHP 8.28.2.361231 Dec 2026
PHP 8.1 and olderNo release—End of life
  • Restart PHP-FPM (or Apache, for mod_php) after upgrading. Running workers keep the old code.
  • Rebuild container images once your base image tag (for example php:8.4-fpm) has been republished, and redeploy.
  • Distribution packages from Debian, Ubuntu, RHEL, and others may backport fixes under their own version numbers. Check the package changelog for the CVE IDs rather than trusting php -v.
  • PHP 8.6.0 also reached general availability today. Do not combine an emergency patch with a minor-version upgrade; take the patch release on your current branch first. Note that 8.6 changes several session defaults, including session.use_strict_mode, session.cookie_httponly, and session.cookie_samesite.
  • PHP 8.2 loses security support in six weeks. Plan the move to 8.4 or 8.5 now.

The fixed releases include the October 21 PHP2Shell fixes (CVE-2026-109618 and CVE-2026-109619, both in CISA’s KEV catalog), so anyone who skipped October gets both with one upgrade. See our October PHP release guide for background.

Triage: the five checks that matter most

Most of the critical issues need a specific setup. Run these on each PHP host to find out which ones apply to you:

CVEYou are exposed if…Quick check
CVE-2026-129289 (FPM smuggling)Your web server reuses FastCGI connections to PHP-FPMnginx -T | grep fastcgi_keep_conn
grep -rn enablereuse /etc/apache2 /etc/httpd
CVE-2026-115560 (session serializer)Code switches session.serialize_handler to php at runtime and upload progress is ongrep -rn serialize_handler src/ vendor/
php -i | grep upload_progress.enabled
CVE-2026-129474 (8.5 backtraces)PHP 8.5 with zend.exception_ignore_args=0php -i | grep exception_ignore_args
CVE-2026-129291 (FPM privilege escalation)A pool sets catch_workers_output = yes and runs untrusted codegrep -rn catch_workers_output /etc/php*
CVE-2026-126714 (session files)You use the default file session handlerphp -i | grep session.save_handler

Run php -i through the same SAPI and pool that serves traffic. The CLI often reads a different php.ini from PHP-FPM, so a quick way to see the real values is a temporary phpinfo() page restricted to your IP, or php-fpm -tt for pool settings.

CVE-2026-129289: PHP-FPM request smuggling

FastCGI lets a web server send many requests to PHP-FPM over one connection. When it does, PHP-FPM has to discard any part of a request body the script did not read before handling the next request on that connection. According to the advisory summaries, it does not always do so. An attacker can shape the leftover body into what looks like a fresh FastCGI request that the front-end server never saw, approved, or logged. Because FastCGI requests can carry PHP settings, that hidden request can switch on options that lead to running attacker-supplied code.

Two conditions must both be true:

  1. The front end reuses FastCGI connections. That means nginx with fastcgi_keep_conn on;, Apache mod_proxy_fcgi with enablereuse=on, or HAProxy FastCGI backends that keep connections open. LiteSpeed LSAPI is reported to be affected for broken requests, but code execution was not confirmed.
  2. The application opens php://input without reading it to the end. Some frameworks create the input stream early, before routing or authentication, and only read it if a controller asks for the body.

Not affected: default nginx and Apache configurations (which open a new FastCGI connection per request) and PHP running as an Apache module (mod_php), which does not use FastCGI.

Connection reuse is a common performance tweak in high-traffic and tuned configurations, and it is frequently set in shared snippets, Helm charts, and control-panel templates rather than by hand, so check the rendered configuration rather than the file you remember editing.

Workaround:

# nginx: remove the directive or turn it off, then reload
#   fastcgi_keep_conn off;
nginx -t && nginx -s reload

# Apache: drop enablereuse=on from ProxyPass / <Proxy> definitions
apachectl configtest && apachectl graceful

This costs some connection setup overhead, which is negligible for most sites. Also make sure the PHP-FPM listener is a Unix socket or bound to localhost and never reachable from the internet; an exposed FPM port has always been remote code execution on its own.

The session bugs: CVE-2026-115560 and CVE-2026-126714

Both session issues end the same way: attacker-influenced data gets unserialized into PHP objects, which can lead to code execution through gadget chains in your application or its dependencies.

  • CVE-2026-115560, session serializer mismatch. PHP published an informational advisory on October 23 and the full fix today. The October PHP2Shell releases did not fix it. You are exposed only if your php.ini sets session.serialize_handler to php_binary or php_serialize, your code switches it to php with ini_set() before session_start(), and session upload progress is enabled, which is the default. Data written in one format and read back in another lets an attacker smuggle serialized objects in through the upload progress feature.
  • CVE-2026-126714, partially overwritten session files. If a write to a session file is cut short, the file can end up holding pieces of two sessions, which PHP then unserializes. This affects the default files save handler, so it is the one most sites have, although triggering it requires the right timing.

Workaround for CVE-2026-115560: set session.upload_progress.enabled = 0 in php.ini, the FPM pool (php_admin_flag[session.upload_progress.enabled] = off), or your web server configuration, then restart every PHP worker. It cannot be changed with ini_set() or .user.ini, because it applies before your script runs. If you already set this for PHP2Shell in October, keep it. Very few applications use upload progress bars built on this feature; check yours before turning it off.

There is no configuration workaround for CVE-2026-126714 beyond moving sessions to Redis, Memcached, or a database handler. Upgrade.

The rest of the release

CVEComponentIssueBranches
CVE-2026-129474CoreUse-after-free in __call() / __callStatic() backtraces can lead to RCE. Workaround: zend.exception_ignore_args=1 (the production default) or fatal_error_backtraces=08.5
CVE-2026-129182CoreUse-after-free via last_fatal_error_backtrace after shutdown8.5
CVE-2026-129496DateTimezone cache use-after-free can lead to RCE; needs startup warnings plus file error loggingAll
CVE-2026-129291FPMepoll use-after-free lets code in a worker take over the FPM master (often root) when catch_workers_output = yes; mainly a shared-hosting riskAll
CVE-2026-129292FPMXSS on the FPM status page through unescaped user and script fieldsAll
CVE-2026-128090PHAROpenSSL-signed PHAR can be downgraded and accepted as hash-signed; matters for PHARs in writable locationsAll
CVE-2026-129538CGIOut-of-bounds read and write during PATH_INFO correction; php-cgi onlyAll
CVE-2026-129506SOAPUse-after-free processing DTD entity referencesAll
CVE-2026-15353SOAPInformation disclosure via malformed array dimensionsAll
CVE-2026-128064StreamsMixed-case HTTPS:// and FTPS:// URLs can be sent unencryptedAll
CVE-2026-127960StreamsDenial of service through folded HTTP response headersAll
CVE-2026-129481SessionUse-after-free after interrupted session shutdown8.5, 8.4, 8.3
CVE-2026-129501DOMDouble free during XML serialization8.5, 8.4
CVE-2026-129438URIIncorrect RFC 3986 serialization for oversized input; bundled uriparser also updated to 1.0.3 (CVE-2026-48841)8.5

While you are checking FPM: the status and ping pages (pm.status_path, ping.path) should never be public. Confirm with curl -s -o /dev/null -w '%{http_code}' https://your-site/status from outside your network; anything other than 403 or 404 deserves a look.

How to upgrade

# Debian / Ubuntu (ondrej/php or distribution packages)
apt-get update && apt-get install --only-upgrade 'php8.4*'
systemctl restart php8.4-fpm

# RHEL / Alma / Rocky (Remi or AppStream)
dnf upgrade 'php*' && systemctl restart php-fpm

# Alpine
apk upgrade -U 'php84*' && rc-service php-fpm84 restart

# Docker: pull the republished tag, rebuild, redeploy
docker pull php:8.4-fpm && docker build --pull -t your-app .

# Verify what is actually serving traffic
php-fpm8.4 -v
curl -sI https://your-site/ | grep -i x-powered-by   # if expose_php is on

Upstream source arrived between 14:00 and 14:30 UTC on November 19. Distribution repositories, official Docker images, and managed hosts follow on their own schedules, from hours to days. If your channel has not published yet, apply the FastCGI and session workarounds now and patch when it lands.

Is anything being exploited?

As of release day, PHP reported no exploitation, no public exploit code was known, and none of these CVEs were in CISA’s KEV catalog. That can change quickly. October’s PHP2Shell bugs went from release to the KEV catalog in five days, and diffing a security release is now fast and cheap. Treat the FastCGI and session issues as urgent if the triage checks above match your setup.

The lesson for API teams: what runs before your auth check

CVE-2026-129289 only bites when a framework touches the request body before routing and authentication decide whether anyone should. CVE-2026-115560 lives in session handling, which runs before your code knows who the user is. Both are reminders that the most dangerous code in an API is often the code that runs for anonymous callers.

  • Know which endpoints accept bodies without authentication. Login, signup, password reset, webhooks, and file uploads are the usual suspects; every one of them is reachable by anyone.
  • Read or reject bodies deliberately. Enforce maximum body sizes at the edge and in PHP (post_max_size), and reject unexpected content types early.
  • Avoid unserializing anything a user could influence. Prefer php_serialize or JSON-based session storage, never change serializers at runtime, and never pass request data to unserialize().
  • Retest after every runtime upgrade. A security patch, a new FPM pool template, or a 8.6 migration with new session defaults can all change how your API behaves at the edges.

How DastPilot helps around a release like this

To be upfront: DastPilot will not tell you whether a server is running PHP 8.4.27 or whether fastcgi_keep_conn is on. Those are host facts; use the checks above, your package inventory, and your image scanner. And sending request smuggling payloads at production to “test” it is a good way to corrupt other users’ requests.

Where dynamic application security testing earns its place is before and after the patch. DastPilot scans your APIs from an OpenAPI spec or Postman collection, as every role you configure. The checks most relevant this week:

  • Missing authentication: calls every documented endpoint with no credentials, so you have a concrete list of which PHP endpoints accept bodies from anonymous users and should be patched and watched first.
  • Improper input handling: sends malformed, oversized, and wrong-content-type bodies to every operation and flags 5xx responses, timeouts, and unexpected successes, which are often the first visible sign that a parser is misbehaving.
  • Broken session and token handling: replays tampered, expired, and malformed session cookies and tokens, and flags endpoints that accept them.
  • Privilege escalation (BFLA) and object access (BOLA): replays admin operations as lower roles and swaps object IDs between users, limiting what an attacker can do with a hijacked session.
  • Regression tracking: each scan is compared with the last, so if the PHP upgrade, a new FPM template, or 8.6’s changed session defaults alter how your auth layer behaves, the finding shows up as new or reopened.

Patch PHP to close these CVEs. Then run DastPilot in your CI/CD pipeline against the upgraded service, so the fix ships with evidence that authentication and authorization still hold.

Frequently asked questions

Which PHP versions fix the November 2026 vulnerabilities?

PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36, released on November 19, 2026. PHP 8.5.13 fixes 17 CVEs, 8.4.28 fixes 14, 8.3.37 fixes 13, and 8.2.36 fixes 12. PHP 8.1 and older are end of life and received no release. Linux distributions may backport the fixes without changing the upstream version number, so check package changelogs for the CVE IDs.

What is CVE-2026-129289?

CVE-2026-129289 is a CVSS 9.2 request smuggling flaw in PHP-FPM, present since PHP 5.6.0. When the web server reuses FastCGI connections and the application opens php://input without reading it to the end, the unread request body can be interpreted as a second, hidden FastCGI request, which can be used to change PHP settings and run attacker code. Default nginx and Apache configurations do not reuse FastCGI connections and are not affected.

How do I mitigate CVE-2026-129289 without upgrading PHP?

Turn off FastCGI connection reuse: remove fastcgi_keep_conn on in nginx, or enablereuse=on in Apache mod_proxy_fcgi, then reload the web server. Make sure the PHP-FPM port or socket is never reachable from the internet. Then upgrade to the fixed PHP release.

Is CVE-2026-115560 the same as PHP2Shell?

No. PHP2Shell (CVE-2026-109618 and CVE-2026-109619) was fixed on October 21, 2026. CVE-2026-115560 is a separate session serializer mismatch that the October releases did not fix. It affects applications that configure session.serialize_handler as php_binary or php_serialize and switch it to php at runtime, with session upload progress enabled. Setting session.upload_progress.enabled=0 in php.ini or the FPM pool blocks the published attack path.

Are the November 2026 PHP vulnerabilities being exploited?

As of November 19, 2026, PHP reported no exploitation, no public exploits were known, and none of the CVEs were in CISA’s Known Exploited Vulnerabilities catalog. The October PHP2Shell bugs were added to the KEV catalog within days of release, so patch promptly.

Can a DAST scanner detect these PHP vulnerabilities?

Not directly. Exposure depends on the PHP version, web server, and php.ini settings, which are best checked on the host. API DAST tools such as DastPilot help by confirming which endpoints accept request bodies without authentication, sending malformed and oversized bodies and sessions to every documented endpoint, and flagging server errors or authorization changes after the upgrade.

Prove your PHP APIs still hold after the patch

DastPilot maps what anonymous callers can reach, fuzzes every documented endpoint with malformed bodies and sessions, tests BOLA and BFLA as each role, and flags regressions on every scan. 30-day free trial, no credit card required.