News Security news

PHP releases 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November 2026, fixing six critical vulnerabilities

The PHP team shipped its pre-announced security releases 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November 2026. They fix 18 vulnerabilities, six of which the project's GitHub advisories rate critical (CVSS 4.0 9.2). The most serious is request smuggling in PHP-FPM: behind a front end that reuses FastCGI connections, an unauthenticated attacker can run their own PHP code with a single request. The team does not mention exploitation.

Kyberkit editorial team · · event date · reading time 5 minutes · updated · For admins and analysts

News: PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix six critical flaws

Key points

  • PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 Nov 2026; the changelog lists 17 GHSA advisories plus a bundled uriparser update, and six advisories are rated critical (CVSS 4.0 9.2).
  • The worst, CVE-2026-129289, hits PHP-FPM behind nginx with fastcgi_keep_conn on or Apache with enablereuse=on: an unauthenticated attacker can run PHP code with one request. Default front-end setups that close the connection after each request are not affected.
  • Other critical bugs: partially overwritten session files (CVE-2026-126714), the ext-date timezone cache (CVE-2026-129496) and three use-after-frees, two of them only in PHP 8.5 (CVE-2026-129474, CVE-2026-129182).
  • Before you can patch: disable FastCGI connection reuse, set session.upload_progress.enabled=0 and, on PHP 8.5, zend.exception_ignore_args=1 or fatal_error_backtraces=0.

On the afternoon of 19 November 2026 the PHP team shipped its pre-announced security releases: 8.5.13, 8.4.28, 8.3.37 and 8.2.36. According to the changelog, they fix 17 bugs that carry their own GHSA advisory and also bump the bundled uriparser library to 1.0.3 (CVE-2026-48841). The project's GitHub Security Advisories rate six of them critical, with a CVSS 4.0 score of 9.2. The team warned on 18 November that the critical issues need non-default configuration or uncommon setups; the advisories now spell out which ones. PHP 8.6.0 also came out the same day.

The critical bugs and when they apply

CVE Component Branches When you are exposed
CVE-2026-129289 PHP-FPM – request smuggling 8.2–8.5 the front end reuses FastCGI connections (nginx fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, some HAProxy setups, LSAPI) and the app leaves php://input partly unread
CVE-2026-126714 sessions – partially overwritten file 8.2–8.5 default files session handler, attacker can influence session contents (e.g. upload progress), and the app has a usable deserialization gadget chain
CVE-2026-129496 ext-date – timezone cache 8.2–8.5 non-thread-safe build, PHP errors logged to a file, and a startup warning (e.g. an invalid date.timezone)
CVE-2026-129481 sessions – interrupted shutdown 8.3–8.5 a fatal error in a callback during session cleanup; follows an incomplete fix for CVE-2026-109619 (PHP2Shell)
CVE-2026-129474 core – magic method backtraces 8.5 only fatal_error_backtraces=1 (default in 8.5) and zend.exception_ignore_args=0; php.ini-production blocks this path
CVE-2026-129182 core – last_fatal_error_backtrace 8.5 only a fatal error at shutdown caused by path-specific configuration, such as Apache per-directory settings

PHP-FPM is the one to worry about. Per advisory GHSA-qc49-hpvq-g2w6, unread request body bytes stay on the shared FastCGI connection and PHP-FPM parses them as the next request. With a single request, an unauthenticated attacker can execute their own PHP code as the worker, run scripts outside the routes the front end exposes, spoof the client IP used for access control, and change admin-level PHP settings that persist on that worker. Default front-end setups that close the FastCGI connection after every request are not affected by the demonstrated attack.

The remaining critical bugs are use-after-frees and race conditions. The advisories confirm worker crashes, while code execution needs extra conditions such as known memory addresses or a favourable heap layout. Among the non-critical fixes: a Phar signature bypass via algorithm downgrade (CVE-2026-128090), XSS in the PHP-FPM status page (CVE-2026-129292), local privilege escalation through epoll in PHP-FPM (CVE-2026-129291, rated high), an out-of-bounds write in PHP-CGI (CVE-2026-129538), and the previously announced CVE-2026-115560 (session serializer mismatch).

The PHP team says nothing about exploitation. The advisories do include detailed technical write-ups, though, and attackers started exploiting the PHP2Shell bugs fixed on 21 October within days.

How to tell if you are exposed

  1. Check every PHP runtime (CLI, PHP-FPM, mod_php): php -v, php-fpm -v or a phpinfo() page served by the pool in question. Anything older than 8.2.36, 8.3.37, 8.4.28 or 8.5.13 is vulnerable (for distro packages, follow your distribution's security notices).
  2. In nginx, look for fastcgi_keep_conn on (grep -rn fastcgi_keep_conn /etc/nginx/); in Apache, look for enablereuse=on on ProxyPass or on a SetHandler pointing at fcgi://.
  3. Find your session handler (session.save_handler) and whether session.upload_progress.enabled is on.
  4. On PHP 8.5, check zend.exception_ignore_args and fatal_error_backtraces in the FPM pool configuration, not just the CLI.

The PHP team has not published indicators of compromise.

What to do

  1. Update to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or your distribution's fixed package. PHP 8.1 and older no longer get fixes from the project.
  2. Restart PHP-FPM, Apache and any other PHP processes – otherwise the old code keeps running.
  3. Until you can patch, turn off FastCGI connection reuse (drop fastcgi_keep_conn on in nginx, enablereuse=on in Apache) and never expose PHP-FPM listeners to untrusted networks.
  4. If you don't need upload progress, set session.upload_progress.enabled=0, and avoid storing large user-supplied data in sessions.
  5. On PHP 8.5, set zend.exception_ignore_args=1 or fatal_error_backtraces=0 in the worker configuration and restart the workers. Changing only the CLI configuration is not enough.
  6. Fix configuration errors and deprecated settings that trigger startup warnings, or send PHP errors to syslog instead of a file.

Timeline

  • 21 Oct 2026 – release fixing PHP2Shell (CVE-2026-109618, CVE-2026-109619), soon exploited.
  • 23 Oct 2026 – the team announces CVE-2026-115560 for the next regular release.
  • 18 Nov 2026 – advance notice of a critical release.
  • 19 Nov 2026 – 8.5.13, 8.4.28, 8.3.37 and 8.2.36 released, advisories published.

Updates

  • 19 Nov 2026 – The fixed versions are out. We rewrote this story from the changelog and the GitHub advisories: 18 fixes, six critical, the conditions that matter and interim mitigations. The original 18 November text covered only the advance notice.

Sources

  1. PHP – PHP 8.5.13 Released! and other releases (19 Nov 2026)
  2. PHP – ChangeLog 8.5.13
  3. PHP – php-src GitHub Security Advisories
  4. GHSA-qc49-hpvq-g2w6 – PHP-FPM request smuggling (CVE-2026-129289)
  5. GHSA-fm2m-fjf5-v3cp – partially overwritten session files (CVE-2026-126714)
  6. PHP – Upcoming Critical PHP Security Release (18 Nov 2026)
  7. PHP – Security advisory: Critical remote code execution vulnerabilities, update now (21 Oct 2026)
  8. PHP – Supported versions

Spotted a mistake? Let us know and we will correct it openly.