On November 19, 2026, the PHP project released PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13, fixing 17 vulnerabilities. Seven are rated critical by the PHP project (CVSS 4.0 9.2), including CVE-2026-115560, a session serializer mismatch that can lead to remote code execution, and CVE-2026-129289, a PHP-FPM request smuggling flaw that lets an unauthenticated attacker forge a backend request and execute attacker-controlled PHP code. PHP 8.6.0, released the same day, already includes the fixes.

PHP runs a large share of the world’s websites and web applications, in virtual machines, containers and managed platforms alike. CVE-2026-115560 was pre-announced in October, a few days after the PHP2Shell fixes (CVE-2026-109618, CVE-2026-109619), with the mitigation of disabling session upload progress. Today’s release publishes its full details and fixes it alongside 16 other vulnerabilities. Several of them need specific configurations, but the release as a whole affects every supported PHP branch.

PHP November 2026 security release: key facts

FactDetail
CVEs17 in total; critical: CVE-2026-115560, CVE-2026-129289, CVE-2026-126714, CVE-2026-129496, CVE-2026-129481, CVE-2026-129474, CVE-2026-129182
TypeDeserialization of untrusted data (CWE-502) in the session extension; HTTP request smuggling (CWE-444) in PHP-FPM; several use-after-free bugs
SeverityRated critical by the PHP project (CVSS 4.0 9.2) for all seven; NVD score pending
Required configurationCVE-2026-115560: session upload progress enabled and mismatched session serializers. CVE-2026-129289: PHP-FPM behind a front end that reuses FastCGI connections
Affected versionsPHP 8.2.0 to 8.2.35, 8.3.0 to 8.3.36, 8.4.0 to 8.4.27 and 8.5.0 to 8.5.12 (some CVEs affect only some branches)
Fixed versions8.2.36, 8.3.37, 8.4.28, 8.5.13; PHP 8.6.0 includes the fixes
ExposureInternet-facing PHP applications; exploitability depends on configuration and on the application
WorkaroundSet session.upload_progress.enabled = 0 (CVE-2026-115560); disable FastCGI connection reuse on the front end (CVE-2026-129289); other CVEs have their own workarounds
ExploitationNo known in-the-wild exploitation; a public proof of concept exists for CVE-2026-115560 in a lab setup

What is CVE-2026-115560?

CVE-2026-115560 is a flaw in PHP’s session upload progress feature. When a client uploads a file, PHP writes the upload’s progress into the user’s session, including a value the client controls. PHP supports several session serialization formats, and if that data is written in one format (php_serialize or php_binary) and later read in another (php), the reader can treat attacker-supplied bytes as serialized object data.

This can happen when an application switches session.serialize_handler at runtime before calling session_start(), or when separate applications, PHP-FPM pools, virtual hosts or command-line jobs with different settings share the same session storage. If the reading application has a suitable deserialization gadget chain, the attacker can execute code with the privileges of the PHP worker. According to the PHP advisory, the original report demonstrated command execution with a Guzzle gadget on PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12, and with a Monolog gadget.

The fix turns session upload progress off by default and blocks runtime changes to session settings while the feature is enabled. An explicit session.upload_progress.enabled = 1 in existing configuration still overrides the new default, and the PHP project notes that matching serializers across separate configurations is still the administrator’s responsibility.

What is CVE-2026-129289?

CVE-2026-129289 is an HTTP request smuggling flaw in PHP-FPM. When an application opens php://input but does not read the request body to the end, PHP can leave the unread bytes on a persistent FastCGI connection. An attacker can place a crafted FastCGI message in that body, and PHP-FPM accepts it as a new request that the web server never created or authorized.

The forged request controls FastCGI parameters, including the script to run and administrator-level PHP settings, which lets the attacker execute attacker-controlled PHP code as the worker in a single unauthenticated request, provided they know the path of an existing PHP script on the server. According to the PHP advisory, no non-default PHP setting, memory corruption or race condition is needed, and the bug has existed since PHP 5.6.0.

Exploitation requires a front end that reuses backend connections, such as nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, or HAProxy FastCGI applications that keep connections open. Standard nginx and Apache configurations that close the FastCGI connection after each request are not affected by the demonstrated attack. LSAPI is affected by the same cleanup bug, but the advisory does not establish code execution through LSAPI.

Which PHP versions are affected?

PHP branchAffected versionsFixed version
8.58.5.0 to 8.5.128.5.13
8.48.4.0 to 8.4.278.4.28
8.38.3.0 to 8.3.368.3.37
8.28.2.0 to 8.2.358.2.36
8.6Not listed as affected8.6.0 (released with the fixes)

These ranges apply to CVE-2026-115560, CVE-2026-129289 and most of the other vulnerabilities in the release; a few affect only some branches (see below). PHP 8.1 and older are end of life and received no release, although the PHP project notes that older versions may also be affected (session upload progress was introduced in PHP 5.4.0). Linux distributions often backport fixes without changing the PHP version number, so check your distribution’s security tracker as well as the version string. PHP bundled in container images and application platforms needs its own update.

Additional vulnerabilities fixed in the same release

The other five critical vulnerabilities (all CVSS 4.0 9.2 according to the PHP project):

  • CVE-2026-126714 (8.2 to 8.5): partially overwritten session files can lead to remote code execution. Requires attacker influence over session data, an interrupted write and a gadget chain. Disabling session upload progress removes one input path but is not a full fix.
  • CVE-2026-129496 (8.2 to 8.5): a timezone cache use-after-free can lead to remote code execution. Requires a startup diagnostic and PHP error logging to a file; code execution was demonstrated locally in PHP-FPM and Apache mod_php under additional assumptions.
  • CVE-2026-129481 (8.3 to 8.5): use-after-free after an interrupted session shutdown. Code execution has not been demonstrated. Disabling session upload progress does not address it.
  • CVE-2026-129474 (8.5 only): use-after-free in magic method backtraces can lead to remote code execution, confirmed by the PHP project on PHP 8.5. It depends on the application and requires bypassing address randomization.
  • CVE-2026-129182 (8.5 only): use-after-free in the fatal error backtrace after shutdown. Code execution through this path has not been demonstrated.

The release also fixes four high-severity issues: a PHP-FPM epoll use-after-free that allows local privilege escalation to root when the FPM master runs as root (CVE-2026-129291, affecting configurations with catch_workers_output enabled, including the official PHP-FPM Docker images), a denial of service through folded HTTP response headers (CVE-2026-127960), mixed-case HTTPS and FTPS URLs that can send data in plaintext (CVE-2026-128064), and a PHAR signature bypass (CVE-2026-128090). Six medium-severity issues affect PHP-CGI, SOAP, DOM, the URI extension and the PHP-FPM status page.

Is there a patch for CVE-2026-115560 and CVE-2026-129289?

Yes. PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13 were released on November 19, 2026 and are available on the PHP downloads page. PHP 8.6.0, released the same day, includes the same fixes. Linux distributions, container image maintainers and hosting platforms that ship PHP need to release their own updated packages.

How to mitigate the PHP vulnerabilities

The best fix is to upgrade to the fixed release for your branch. Each critical vulnerability has a different workaround, and no single setting covers all of them.

  • Inventory: find every PHP installation, including PHP in container images, PHP-FPM pools and application platforms, and note which ones run PHP-FPM behind nginx, Apache or HAProxy.
  • Upgrade: move to PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 or 8.6.0, then restart the PHP master process and all workers.
  • CVE-2026-115560: set session.upload_progress.enabled = 0 in php.ini or the FPM pool configuration. Calling ini_set() from the application is too late. Check for explicit settings that re-enable it, even after upgrading.
  • CVE-2026-129289: disable FastCGI connection reuse: leave nginx fastcgi_keep_conn off, leave Apache enablereuse off, or configure other front ends to close the backend connection after each request. Never expose PHP-FPM listeners to untrusted networks.
  • CVE-2026-129474 and CVE-2026-129182 (PHP 8.5): set zend.exception_ignore_args = 1 or fatal_error_backtraces = 0.
  • CVE-2026-129496: fix configuration errors that produce startup warnings, or send PHP errors to syslog instead of a log file.
  • CVE-2026-129291: disable catch_workers_output in affected FPM pools, and avoid running the FPM master as root where possible.
  • Prioritize internet-facing PHP-FPM servers behind connection-reusing front ends, and applications that share session storage or change session settings at runtime.

Is CVE-2026-115560 being exploited in the wild?

There are no known reports of in-the-wild exploitation of any of the vulnerabilities, and none is listed in CISA’s Known Exploited Vulnerabilities catalog. A public proof-of-concept exploit for CVE-2026-115560 has been available on GitHub since October, but it targets a deliberately vulnerable lab application with a built-in gadget. With full technical details for all 17 vulnerabilities now public, especially for the PHP-FPM request smuggling flaw, exploit attempts are likely to follow.

How can Orca help?

Orca enables customers to quickly identify assets running vulnerable PHP versions, including PHP installed from OS packages and PHP bundled in container images, and to understand their exposure in context, including internet accessibility, runtime reachability and asset criticality, so they can prioritize remediation based on real risk rather than CVSS alone.