November 18, 2026

PHP critical security release, 19 November (CVE-2026-129289, CVE-2026-115560)

This page will be continuously updated as we have more information

TL;DR

  • PHP released security updates for all supported versions on 19 November 2026. Fixed versions: 8.5.13, 8.4.28, 8.3.37 and 8.2.36.
  • The release fixes 18 CVEs, including CVE-2026-129289, a critical PHP-FPM request smuggling flaw (CVSS 9.2). With a single request, an unauthenticated attacker can run PHP code as the worker if your web server reuses connections to PHP-FPM and an application opens php://input without reading it fully.
  • PHP rated the highest-severity issue critical. According to PHP, the critical issues only affect installations with non-default configuration or uncommon setups.
  • CVE-2026-115560 is one of several critical issues in this release. If you already set session.upload_progress.enabled=0 and restarted your PHP workers, the published attack path for that CVE is mitigated, so we don’t recommend taking your application offline for it while you wait to update. That setting doesn’t cover the other critical issues, so upgrade as soon as you can.
  • Aikido Images for PHP already include these fixes for Aikido users, with more images on the way. Everyone else can pull them from the public ECR gallery.
  • To check whether you're affected, click "Am I affected?" on your Aikido dashboard.

Am I affected?

Click "Am I affected?" on your Aikido dashboard to see whether your projects run an affected PHP version. Any PHP version earlier than the fixed versions in this release is in scope, though not every issue applies to every branch. The PHP 8.5.13 changelog lists these security fixes, and each CVE links to its advisory. PHP's changelog doesn't give severity ratings, so check the advisory for details.

CVE Component Issue
CVE-2026-115560 Session Session serializer mismatch can lead to remote code execution
CVE-2026-126714 Session Partially overwritten session files can lead to remote code execution
CVE-2026-129481 Session Use-after-free after interrupted session shutdown
CVE-2026-129474 Core Use-after-free in magic method backtraces can lead to remote code execution
CVE-2026-129182 Core Use-after-free via repopulation of the last fatal error backtrace global after shutdown
CVE-2026-129496 Date Timezone cache use-after-free can lead to remote code execution
CVE-2026-129501 DOM Double free during DOM XML serialization
CVE-2026-129538 CGI PHP-CGI out-of-bounds read and write during PATH_INFO correction
CVE-2026-129291 FPM epoll use-after-free can lead to local privilege escalation
CVE-2026-129289 FPM Request smuggling through an unread HTTP request body
CVE-2026-129292 FPM Status endpoint XSS via unescaped user and script fields
CVE-2026-128090 Phar OpenSSL signature bypass via algorithm downgrade
CVE-2026-15353 SOAP Information disclosure through malformed array dimensions
CVE-2026-129506 SOAP Use-after-free when processing DTD entity references
CVE-2026-128064 Standard Mixed-case HTTPS and FTPS URLs can expose data in plaintext
CVE-2026-127960 Standard Denial of service through folded HTTP response headers
CVE-2026-129438 URI Incorrect RFC 3986 URI serialization for oversized input
CVE-2026-48841 URI Upgrade to uriparser 1.0.3

CVE-2026-129289 exposure

PHP's advisory says exploitation needs a front end that enables persistent backend connections and an application path that opens php://input without reading it fully. Relevant configurations include nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy FastCGI applications that retain backend connections, and LSAPI. Standard nginx and Apache configurations that close the FastCGI connection after each request aren't affected by the demonstrated attack.

Affected versions are 8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28 and 8.5 before 8.5.13.

CVE-2026-115560 configuration

On 23 October, PHP published an informational advisory for CVE-2026-115560 and said the full advisory would follow with the next regular release. The 19 November releases are that release. An application is only exposed to CVE-2026-115560 if both of these conditions hold:

  • Its configuration sets session.serialize_handler to php_binary or php_serialize, and its code switches the handler to php with ini_set() before calling session_start().
  • Session upload progress is enabled, which is PHP's default.

The 21 October releases that fixed PHP2Shell don't include a fix for this issue.

Upgrade PHP

Upgrade to the fixed version for your branch. Source and Windows downloads are on the PHP downloads page.

PHP branch Fixed version
8.5 8.5.13
8.4 8.4.28
8.3 8.3.37
8.2 8.2.36

Use Aikido Images

Aikido Images for PHP already include the fixes from the 19 November releases, and we're adding more images. Aikido users can get them from Aikido Images. Everyone else can pull them from the public ECR gallery.

PHP branchAffected versionsFixed inAikido patched imagesNotes
8.5Every release before 8.5.138.5.13
Available (15)
php:8-cli
php:8.5-apache-trixie
php:8.5.11-cli-alpine3.24
php:8.5.12
php:8.5.12-alpine3.23
php:8.5.12-alpine3.24
php:8.5.12-apache
php:8.5.12-cli
php:8.5.12-cli-alpine3.23
php:8.5.12-cli-alpine3.24
php:8.5.12-fpm
php:8.5.12-fpm-alpine3.23
php:8.5.12-fpm-alpine3.24
php:8.5.12-fpm-trixie
php:8.5.12-trixie
8.4Every release before 8.4.288.4.28
Available (14)
php:8.4-cli
php:8.4-fpm-bookworm
php:8.4.26-alpine3.23
php:8.4.26-fpm-alpine3.24
php:8.4.27
php:8.4.27-alpine3.23
php:8.4.27-alpine3.24
php:8.4.27-apache
php:8.4.27-cli
php:8.4.27-fpm
php:8.4.27-fpm-alpine3.23
php:8.4.27-fpm-alpine3.24
php:8.4.27-fpm-trixie
php:8.4.27-trixie
8.3Every release before 8.3.378.3.37
Available (4)
php:8.3-apache-bookworm
php:8.3-fpm-bookworm
php:8.3.36-apache
php:8.3.36-cli
8.2Every release before 8.2.368.2.36
Available (8)
php:8.2.35
php:8.2.35-alpine3.24
php:8.2.35-apache
php:8.2.35-cli
php:8.2.35-cli-alpine3.24
php:8.2.35-fpm
php:8.2.35-fpm-alpine3.24
php:8.2.35-fpm-trixie
End of life December 31, 2026
8.1 and 8.0Treat all as affectedNo upstream fix
Available (1)
php:8.1-fpm-alpine3.21
Aikido backport
7.4Treat all as affectedNo upstream fix
Available (7)
php:7.4-apache
php:7.4-fpm-bullseye
php:7.4.33
php:7.4.33-apache
php:7.4.33-cli
php:7.4.33-fpm
php:7.4.33-fpm-alpine
Aikido backport
7.0 to 7.3Treat all as affectedNo upstream fix
Available (13)
php:7.0.33
php:7.0.33-apache
php:7.0.33-cli
php:7.0.33-fpm
php:7.1.33
php:7.1.33-apache
php:7.1.33-cli
php:7.1.33-fpm
php:7.1.33-fpm-alpine
php:7.2.34
php:7.2.34-apache
php:7.2.34-cli
php:7.2.34-fpm
Aikido backport
5.5 and 5.6Treat all as affectedNo upstream fix
Available (3)
php:5.6.40
php:5.6.40-apache
php:5.6.40-fpm
Aikido backport

Why do the tags still show the previous version number? We backport security fixes into our images instead of bumping to the upstream release, so the tag keeps its original version number (for example 8.5.12) while the image contains the 19 November fixes. You don't need to wait for an 8.5.13 tag.

Mitigate until you've upgraded

CVE-2026-129289: Turn off backend connection reuse on your front end (the settings listed above), or configure it to close the connection after every request. Reading php://input to the end isn't a reliable fix on its own, because PHP says error paths, resource exhaustion and application shutdown can still leave bytes unread. Don't expose PHP-FPM or LSAPI listeners directly to untrusted networks.

CVE-2026-115560:

  1. Set session.upload_progress.enabled=0. PHP's October guidance for this setting says to apply it in php.ini, an FPM pool or your server configuration.
    • The guidance says the setting has to apply before request parsing, so don't use ini_set() or an FPM .user.ini file to change it.
    • If you already applied it as a mitigation for CVE-2026-109619 in October, keep it in place.
  2. Restart every PHP worker so the setting takes effect.
  3. Search your code for runtime calls that switch session.serialize_handler to php. PHP says applications that never change the serialize handler at runtime can keep session upload progress enabled.

‍

If you haven't patched PHP2Shell yet

CVE-2026-109618 and CVE-2026-109619, known together as PHP2Shell, are a separate pair of critical vulnerabilities that PHP fixed on 21 October in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The 19 November releases include those fixes, so upgrading to the versions above covers both. Our PHP2Shell post has the details.

‍

4.7/5
Tired of false positives?

Try Aikido like 100k others.
Start Now
Get a personalized walkthrough

Trusted by 100k+ teams

Book Now
Scan your app for IDORs and real attack paths

Trusted by 100k+ teams

Start Scanning
See how AI pentests your app

Trusted by 100k+ teams

Start Testing
Authors
Dania Durnas
Developer Content Writer
Scan for malware
Secure your code, cloud, and runtime in one central system. Find and fix vulnerabilities fast automatically.
Start for free
Share:

Recently Added

November 19, 2026

Ruby2Shell: critical Ruby RCE, affected versions and how to fix it (CVE-2026-132825)

Ruby2Shell is a critical Ruby flaw that can let an unauthenticated attacker run code on your server, and GitLab is among the affected software. Here is who is exposed, which versions fix it, and what to do until your vendor ships a patch.
Read more
November 18, 2026

nginx2root: Critical nginx vulnerabilities, including one RCE [CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425]

nginx2root is five critical nginx RCE vulnerabilities, including CVE-2026-123007 in HTTP/2. Check if you’re affected and update to nginx 1.31.9 or 1.30.7.
Read more
November 17, 2026

Java4Shell: RCE flaw in OpenJDK's Base64 decoder, with affected versions and fix (CVE-2026-114938)

Java4Shell is a flaw in OpenJDK’s Base64 decoder that can let attackers run code remotely, sometimes without authentication. Here are the affected versions, the fixed builds and how to mitigate it today.
Read more