Security Guides

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 (19 November 2026): 18 fixes, 7 critical, including PHP-FPM request smuggling (CVSS 9.2). What to do today

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix 18 flaws, 7 of them critical, including PHP-FPM CVE-2026-129289. Who is affected and how to update.

Published 2026-11-20 Updated 2026-11-20 Last verified 2026-11-20 11 min read
On this page

For: anyone running websites or systems on PHP (company sites, e-commerce, CMSs such as WordPress, frameworks such as Laravel), and the IT staff, web agencies and maintenance contractors who look after them. This article is based on php.net, the php/php-src security advisories on GitHub and CVE.org records. It does not cover how to attack.

Developing: this article will be updated as more is published

Who is affected

anyone running websites or systems on PHP (company sites, e-commerce, CMSs such as WordPress, frameworks such as Laravel), and the IT staff, web agencies and maintenance contractors who look after them.

Confirmed so farSee the table ↓
  • Releases
  • Number of fixes
  • Severity
1 more
  • CVSS
Not yet confirmed
  • Per-distributor, per-container-image and per-hosting-provider status (not checked by this site)
  • Whether any item is exploited (not mentioned in the php.net release notes or the GitHub advisories; a KEV listing is not confirmed either)
  • An official fix for 8.1 and earlier (php.net updates cover 8.2 to 8.5 only)
What to do nowSee the steps ↓
  1. Check your PHP version
  2. Update to the latest release of your branch
  3. Check the front-end configuration for PHP-FPM
3 more
  1. Check what your distributor or provider has applied
  2. Rebuild containers
  3. Plan a move off old branches
Last checked
As of November 20, 2026 (JST)
Follow-up plans and what we checked

On 19 November 2026 php.net released PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 as security releases and encourages users of each branch to upgrade. The advisories for php/php-src on GitHub were published the same day, and the CVE.org records are public.

What to do today

1

Check your PHP version

Run php -v on the server. Web PHP and command-line PHP can be different versions, so also check the web side, for example with phpinfo() or an admin screen (Checking web and CLI after a PHP update).

2

Update to the latest release of your branch

Move to 8.5.13 on 8.5, 8.4.28 on 8.4, 8.3.37 on 8.3 or 8.2.36 on 8.2. Back up first, and afterwards test the main functions (login, payment, file upload). If you use PHP-FPM, restart the PHP-FPM service after updating and confirm it runs the new version.

3

Check the front-end configuration for PHP-FPM

The CVE-2026-129289 record describes a problem when the front-end server reuses connections to PHP-FPM (for example nginx with fastcgi_keep_conn on, or Apache mod_proxy_fcgi with enablereuse=on). The record says neither is the default. Check whether your configuration has them. This is a check for the time until you update, not a replacement for updating.

4

Check what your distributor or provider has applied

If PHP came from a Linux package (Debian, Ubuntu, RHEL family and so on), check each distributor's information to see whether a fixed version has been released. On shared hosting, check the PHP version your site uses in the control panel and the provider's notices. If a managed service runs it for you, ask when it will be applied. This site has not confirmed the status of each distributor or provider.

5

Rebuild containers

With Docker and similar, check the PHP version in the image you use, rebuild with an image that includes the fix and replace the running containers. The CVE-2026-129291 record says catch_workers_output is enabled in the official PHP-FPM Docker images. Rebuild once the base image has caught up with the fixed versions.

6

Plan a move off old branches

According to php.net, PHP 8.2 security support ends on 31 December 2026, and 8.1 and earlier are already out of support. Plan the move to 8.3, 8.4 or 8.5 now (this site's advice).

What was fixed on which branch

PHP branches and this round of fixes (php.net)
PHP 8.5.13
18 fixes, every item. Under php.net's active support until 31 December 2027
PHP 8.4.28
14 fixes. The 8.4 branch has active support until 31 December 2026 and security support until 31 December 2028
PHP 8.3.37
13 fixes. The 8.3 branch is in security-only support until 31 December 2027
PHP 8.2.36
12 fixes. The 8.2 branch is in security-only support until 31 December 2026
PHP 8.1 and earlier
No php.net update. GitHub advisories include items that affect the 8.1 line (CVE-2026-129291, CVE-2026-127960), with the patched version listed as none
PHP 8.6.0
A new branch released the same day (19 November). Active support until 31 December 2028

The counts differ because each item affects different branches. For example, the two engine items (CVE-2026-129474, CVE-2026-129182) affect only 8.5, the session item CVE-2026-129481 affects 8.3 and later, and the DOM item CVE-2026-129501 affects 8.4 and later.

The seven critical items (official records)

These are rated Critical in GitHub's php/php-src advisories and have a CVSS v4.0 score of 9.2 in the CVE.org records. Technical details are in the linked advisories.

Seven critical items (published 19 November 2026)
CVE-2026-129289 (PHP-FPM)
Request smuggling. When the application opens php://input without reading it to the end and the front-end server reuses connections (nginx with fastcgi_keep_conn on, or Apache mod_proxy_fcgi with enablereuse=on; neither is the default), PHP-FPM can parse leftover bytes as a new FastCGI request. An unauthenticated remote attacker could reach execution of PHP code. With LSAPI, subsequent requests on the connection can be disrupted. Before 8.2.36, 8.3.37, 8.4.28 and 8.5.13
CVE-2026-129496 (Date)
A timezone cache use-after-free. In non-thread-safe builds that write a startup diagnostic to a file-based error_log, an unauthenticated remote attacker can crash PHP-FPM, mod_php or CGI workers. The record says code execution was demonstrated with known memory addresses. All branches from 8.2 to 8.5
CVE-2026-126714 (Session)
With the default files session handler, an interrupted write can leave a file mixing old and new session data. Under certain conditions in the application, this can lead to code execution. All branches from 8.2 to 8.5
CVE-2026-115560 (Session)
A session serializer mismatch. When session upload progress is enabled and the serializer differs between writing and reading, it can lead to code execution, session corruption or denial of service. This is the third issue disclosed after October's emergency update, and it is fixed now. All branches from 8.2 to 8.5
CVE-2026-129474 (Core)
A use-after-free in backtraces of magic method calls (__call, __callStatic). Under conditions such as a fatal memory-limit error, it can lead to memory corruption, a worker crash and possibly code execution. php.ini-production enables a setting that prevents this (zend.exception_ignore_args). 8.5 only
CVE-2026-129182 (Core)
A use-after-free from the fatal error backtrace being repopulated after shutdown. It needs specific configuration such as per-directory settings, and can lead to memory corruption, a worker crash and possibly code execution. 8.5 only
CVE-2026-129481 (Session)
A use-after-free after an interrupted session shutdown. It can crash the worker or corrupt memory. The record says code execution has not been demonstrated. 8.3 and later

Other fixes

Items rated High and Medium
High (4)
A PHP-FPM epoll use-after-free leading to local privilege escalation (CVE-2026-129291, CVSS 8.8; the record says catch_workers_output is enabled in the official PHP-FPM Docker images). Mixed-case URLs such as HTTPS:// handled over unencrypted connections (CVE-2026-128064, CVSS 8.2). Denial of service through folded HTTP headers (CVE-2026-127960, CVSS 8.7). A Phar OpenSSL signature verification bypass (CVE-2026-128090, CVSS 7.7)
Medium (6)
XSS in the PHP-FPM status endpoint (CVE-2026-129292). PHP-CGI out-of-bounds read and write (CVE-2026-129538). A double free in DOM XML serialization (CVE-2026-129501). SOAP information disclosure (CVE-2026-15353) and use-after-free (CVE-2026-129506). Incorrect URI serialization (CVE-2026-129438). The ChangeLog also lists an update of the bundled uriparser to 1.0.3 (CVE-2026-48841)

Who is affected

This site's reading, based on what the advisories and records say:

  • Servers that run PHP-FPM behind nginx or Apache configured to reuse connections should update first. But every PHP-FPM needs the update, whatever its configuration.
  • PHP that handles web requests (PHP-FPM, mod_php, CGI) is the scope named in the timezone cache record (CVE-2026-129496).
  • Applications that store sessions in files (the default) and enable upload progress are more likely to meet the conditions of the two session items.
  • Applications that fetch external URLs may be exposed to the HTTPS case-sensitivity issue (CVE-2026-128064) and the header issue (CVE-2026-127960).
  • Shared servers or containers where other people's PHP code runs match the CVE-2026-129291 record's description of a local attacker who can run PHP code in a worker.

What is known and not known

ItemWhat was publishedStatus
Releases8.5.13, 8.4.28, 8.3.37, 8.2.36, 19 November 2026Confirmed (php.net)
Number of fixes18 in 8.5.13, 14 in 8.4.28, 13 in 8.3.37, 12 in 8.2.36Confirmed (ChangeLog)
Severity7 Critical, 4 High, 6 Medium (GitHub advisories; plus one uriparser update)Confirmed (GitHub)
CVSSThe seven critical items are CVSS v4.0 9.2Confirmed (CVE.org)
8.1 and earlierNo php.net update. Advisories list items that affect 8.1No fix
Distributor and provider statusNot checked by this siteNot confirmed
ExploitationNot mentioned in php.net notes or GitHub advisories; KEV not confirmedNot stated

If someone else runs your site

Ask your web agency, maintenance contractor or hosting provider these three things:

  • Which PHP version does our site run, and when will it move to the latest release of the branch (8.5.13, 8.4.28, 8.3.37 or 8.2.36)?
  • Do you use PHP-FPM, and is the front-end server configured to reuse connections?
  • If we are on PHP 8.2 or earlier, is there a migration plan before 31 December 2026?

Timeline

  1. 21 October 2026

    PHP's emergency update (8.5.12, 8.4.27, 8.3.36, 8.2.35) is released. See the October emergency update explainer.
  2. 23 October 2026

    A third issue not fixed by the October update (CVE-2026-115560) is disclosed.
  3. 19 November 2026

    PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 are released. The third issue (CVE-2026-115560) is fixed too. PHP 8.6.0 is released the same day.
  4. 20 November 2026

    This site checks php.net, the GitHub advisories and CVE.org, and publishes this article.

Sources (official)

Checked on 20 November 2026.

  • php.net, "ChangeLog (PHP 8)" — php.net
  • php.net, "Supported Versions" — php.net
  • GitHub, php/php-src security advisories (for example, PHP-FPM request smuggling, GHSA-qc49-hpvq-g2w6) — github.com
  • CVE.org, "CVE-2026-129289" — cve.org

Update history

2026-11-20: first version, based on the php.net ChangeLog, the GitHub advisories and the CVE.org records. Per-distributor and per-provider status and a CISA KEV listing could not be confirmed.

Latest breaking reports

All breaking reports →

FAQ

QWhat happened?
A

On 19 November 2026 the PHP team released the security releases PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The 8.5.13 ChangeLog lists 18 fixes with CVE numbers. The new branch PHP 8.6.0 was released the same day. php.net encourages users of each branch to upgrade.

QWhat is the most serious fix?
A

Seven are rated Critical in GitHub advisories, and the CVE.org records give all seven a CVSS v4.0 score of 9.2. PHP-FPM request smuggling (CVE-2026-129289) affects every branch from 8.2 to 8.5. The timezone cache (CVE-2026-129496) and session issues (CVE-2026-126714, CVE-2026-115560) are also described as able to lead to code execution.

QIs everyone running PHP-FPM at risk?
A

The CVE-2026-129289 record describes a problem when the front-end server reuses connections to PHP-FPM. Its examples are nginx with fastcgi_keep_conn on and Apache mod_proxy_fcgi with enablereuse=on, and the record says neither is the default in nginx or Apache. It also applies when the application opens php://input without reading it to the end. Check your own server configuration. You should update regardless of that configuration.

QWhich version should I update to?
A

8.5.13 for the 8.5 branch, 8.4.28 for 8.4, 8.3.37 for 8.3 and 8.2.36 for 8.2. The number of fixes differs by branch (18 in 8.5.13, 14 in 8.4.28, 13 in 8.3.37, 12 in 8.2.36). PHP 8.2 security support ends on 31 December 2026, so plan a move to a newer branch too.

QI run PHP 8.1 or earlier. Will there be a fix?
A

php.net released updates for 8.2 to 8.5 only. GitHub advisories list two items that affect the 8.1 line (CVE-2026-129291, the PHP-FPM epoll issue, and CVE-2026-127960, folded HTTP headers), with no patched version. For 8.1 and earlier, check whether your OS distributor or a long-term-support vendor ships its own fix, or move to a supported branch.

QWhat about shared hosting and Docker?
A

On shared hosting the provider usually updates PHP, so check the PHP version your site uses in the control panel and the provider's notices. With Docker, check the PHP version in your image, then rebuild with an image that contains the fix and replace the running containers. The CVE-2026-129291 record says catch_workers_output is enabled in the official PHP-FPM Docker images. For Linux packages, check each distributor's information to see whether the fix has landed.

QIs it being attacked already?
A

As of 20 November 2026, neither the php.net release notes nor the GitHub advisories mention exploitation. The CVE-2026-129496 record does say code execution was demonstrated with known memory addresses. This site has not confirmed a listing in the US CISA Known Exploited Vulnerabilities catalog (KEV). Things move quickly after disclosure, so check for follow-ups.