PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on November 19, 2026, fixing four critical flaws in PHP-FPM, sessions and date handling. If you run any PHP 8.2 to 8.5 release older than those, update today and restart every PHP process; the CLI version alone does not prove the web server is fixed.

Which PHP versions are affected? {#affected}

Every 8.2, 8.3, 8.4 and 8.5 release before the fixed ones, according to the php-src security advisories published on November 19, 2026. PHP's notice the day before said the critical issues need non-default configurations or uncommon setups, so whether you are exposed depends on how PHP runs, but the fix is the same for everyone.

CVE (CVSS v4) Where Needs
CVE-2026-129289 (9.2) PHP-FPM, LSAPI PHP-FPM: persistent FastCGI connections (FCGI_KEEP_CONN) and code that opens php://input without reading it to the end. LSAPI: persistent LSAPI connections and the same unread-body condition
CVE-2026-115560 (9.2) Sessions Session upload progress on, and one session store written with php_binary or php_serialize and read with php
CVE-2026-126714 (9.2) Sessions, files handler (the default) A session write that is interrupted partway through
CVE-2026-129496 (9.2) Date extension A startup warning written to PHP's file-based error_log, in a non-thread-safe build

The same release also fixes a high-severity Phar signature bypass (CVE-2026-128090) and five medium flaws in SOAP, DOM, PHP-CGI and the FPM status page.

The command-line version can differ from the one the web server runs, so check both. On a PHP-FPM host:

php -v # the CLI binary php-fpm -v # the FPM binary (on Debian/Ubuntu: php-fpm8.3 -v, etc.) php-fpm -i | grep -E 'session.upload_progress.enabled|session.serialize_handler|session.save_handler' 

php-fpm -i shows the binary's main configuration; pool files and virtual hosts can override it, so check those too.

On Windows (IIS, XAMPP, Laragon, WampServer), PHP-FPM does not run; IIS uses php-cgi.exe through FastCGI. In PowerShell:

php -v # the PHP on your PATH & "C:\Program Files\PHP\php-cgi.exe" -v # the one IIS runs (use your install path, e.g. C:\xampp\php) php -i | Select-String "session.upload_progress.enabled|session.serialize_handler" 

Then recycle the IIS application pool, or restart Apache in the XAMPP or WampServer control panel, so the new PHP is the one serving pages.

Distribution packages (Debian, Ubuntu, RHEL and others) often backport fixes without changing the upstream version number, so read your distribution's advisory for the package revision that contains these fixes.

Fix it now {#fix}

  1. Install the fixed release for your branch: 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or your distribution's patched package. Container images need a rebuild on a patched base image.
  2. Restart every PHP process: PHP-FPM, Apache with mod_php, queue workers and cron jobs that keep PHP running. Old workers keep the old code in memory.
  3. Verify the running web service and each pool or instance after the restart. For distribution packages, compare the installed package revision with the vendor advisory; an upstream PHP version string alone cannot confirm a backport. If you use a temporary page that prints PHP_VERSION, restrict access to it and remove it right after.
  4. Keep session.upload_progress.enabled=0 unless you use upload progress bars. The fix turns it off by default, but an explicit 1 in php.ini, a pool file or a virtual host overrides the new default.

If you cannot update today, use the advisories' temporary measures; none replaces the update.

  • CVE-2026-115560: set session.upload_progress.enabled=0 in every configuration that can write to the affected session store, checking pool and virtual-host overrides (a pool set to 1 overrides 0 in php.ini), then restart and verify the effective setting for each web context. Do not rely on ini_set() or FPM .user.ini: the setting must be in place before PHP reads the request.
  • CVE-2026-129289: the advisory recommends disabling backend connection reuse between the web server and PHP-FPM until you are patched.
  • CVE-2026-129496: fix whatever produces diagnostics at PHP startup, including warnings and deprecations, or send PHP's errors to a non-file destination, then restart the FPM or Apache master and its workers.

Older, unsupported PHP releases may also be affected, according to the serializer advisory; move them to a maintained branch or a vendor-supported fix.

Why it is dangerous {#why}

Under specific conditions, each can lead to code execution with the PHP worker's privileges, and each sits in a part of PHP that application developers rarely look at. For LSAPI, the FPM advisory documents disruption of later requests, not code execution.

PHP-FPM request smuggling starts with connection reuse: one FastCGI connection can carry several requests. Before taking the next one, PHP must read or discard the rest of the previous request body. According to the advisory, opening php://input without reading it made PHP skip that cleanup, so leftover body bytes could be parsed as a new FastCGI request that never passed through the web server's routing or access rules.

The session serializer mismatch exists because PHP can store sessions in three formats. Upload progress writes attacker-supplied data into the session. If another reader, such as a second pool, a virtual host or a cron job sharing the same session folder, reads it in the php format, part of the key can be decoded as serialized objects. The advisory says objects may be created and their callbacks run before the record is rejected; with a suitable class in the application (a "gadget chain"), that becomes code execution.

Partially overwritten session files come from the default files handler, which wrote new session data over the old file without clearing it first. An interrupted write could leave the new start glued to the old end, and the combined bytes could decode as objects on the next session_start().

The timezone cache use-after-free begins at startup: a warning logged then could leave PHP pointing at freed memory for formatting log timestamps. A later warning during the first request, such as hitting max_input_vars, could touch that memory, which may already hold request data.

What our lab checked {#lab}

We built a read-only checker for the session serializer flaw and ran it on November 19, 2026. It reads PHP versions and the session settings in php.ini, FPM pools and code, and labels each setup affected, mitigated or patched. The vulnerability assessment classifies configuration fixtures; the lab also checks that normal sessions and uploads still work. It does not reproduce the vulnerability.

Terminal output of our PHP session configuration checker: 10 of 10 synthetic setups flagged as affected, 10 of 10 cleared after one change, 11 of 11 control setups unchangedOur checker on 10 synthetic setups and 11 controls, run November 19, 2026.

On 10 synthetic setups, it flagged all 10 as affected. All 10 were classified patched or mitigated after a relevant change: updating, turning upload progress off before request input is read, or separating incompatible session stores. All 11 controls were unchanged: nine configuration fixtures, plus a normal session and a plain file upload that kept working.

One setup stayed flagged after the update alone, by design: upload progress explicitly on, with two pools sharing one session store in different formats. The advisory says the fix does not force separate configurations to agree, so in that case you still need one serializer per store, or separate stores. When you change a store's format, migrate or expire its old records.

Development machines need the update too: local stacks such as XAMPP, Laragon or WampServer on Windows ship their own PHP and keep the old version until you update the stack.

Our take {#our-take}

For most servers, updating and restarting is the whole fix. Upload progress needs more care: if you rely on it, keep every application, pool and job that touches a session store on the same session.serialize_handler, or give them separate stores. Our earlier guide to the October PHP2Shell flaws has more on confirming that FPM and mod_php run the new build, and common PHP security mistakes covers the deserialization risk behind two of these flaws.

Based on the php-src security advisories and php.net release notes of November 18 and 19, 2026. Our lab classified configurations and checked normal sessions and uploads; it did not reproduce any of these flaws.