MOOBON

PHP 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36 Security Release (November 2026)Fixed vulnerabilities and how to update

Published November 21, 20267 min read

On November 19, 2026, PHP 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36 were published as security releases. All supported versions are affected, and the highest severity is CRITICAL. This article lists the fixed vulnerabilities, the setups that are more exposed, and how to check and update your PHP.

This article is based on information published on php.net as of November 21, 2026. Check each distribution's security notices for the status of fixed packages.

1. Overview of the release

DateWhat happened
2026-11-18php.net posted "Upcoming Critical PHP Security Release": releases on November 19, 14:00–14:30 UTC, fixing vulnerabilities that affect all supported PHP versions, with a highest severity of CRITICAL.
2026-11-19PHP 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36 were published as security releases. PHP 8.6.0, a new minor version, was released the same day and contains the same fixes.
  • Part of the regular release cycle. The php.net notice describes it as part of the regular four-week release cycle.
  • The CRITICAL issues need non-default configuration or uncommon setups. php.net says the issues rated CRITICAL require either non-default configuration or uncommon setups. The notice and release pages do not state the severity of each CVE, so check the individual advisories listed in section 2.
  • Separate from October's php2shell. We covered the October 2026 php2shell issues (CVE-2026-109618 / 109619, fixed in 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35) in this article. CVE-2026-115560, which php.net said on October 23 would get a full advisory with the next release, is fixed in this release.

2. Fixed vulnerabilities

The PHP 8.5.13 ChangeLog lists 18 CVEs. "Branches" shows which branches list the entry in the ChangeLog of this release.

AreaIssueCVEBranches
CoreUse-after-free in magic method backtraces can lead to remote code executionCVE-2026-1294748.5
CoreUse-after-free via repopulation of last_fatal_error_backtrace global after shutdownCVE-2026-1291828.5
CGIPHP-CGI out-of-bounds read and write during PATH_INFO correctionCVE-2026-1295388.5 / 8.4 / 8.3 / 8.2
DateTimezone cache use-after-free can lead to remote code executionCVE-2026-1294968.5 / 8.4 / 8.3 / 8.2
DOMDouble free during DOM XML serializationCVE-2026-1295018.5 / 8.4
FPMPHP-FPM epoll use-after-free can lead to local privilege escalationCVE-2026-1292918.5 / 8.4 / 8.3 / 8.2
FPMPHP-FPM request smuggling through an unread HTTP request bodyCVE-2026-1292898.5 / 8.4 / 8.3 / 8.2
FPMPHP-FPM status endpoint XSS via unescaped user and script fieldsCVE-2026-1292928.5 / 8.4 / 8.3 / 8.2
PharPHAR OpenSSL signature bypass via algorithm downgradeCVE-2026-1280908.5 / 8.4 / 8.3 / 8.2
SessionPartially overwritten session files can lead to remote code executionCVE-2026-1267148.5 / 8.4 / 8.3 / 8.2
SessionSession serializer mismatch can lead to remote code executionCVE-2026-1155608.5 / 8.4 / 8.3 / 8.2
SessionUse-after-free after interrupted session shutdownCVE-2026-1294818.5 / 8.4 / 8.3
SOAPSOAP information disclosure through malformed array dimensionsCVE-2026-153538.5 / 8.4 / 8.3 / 8.2
SOAPSOAP use-after-free when processing DTD entity referencesCVE-2026-1295068.5 / 8.4 / 8.3 / 8.2
StandardMixed-case HTTPS and FTPS URLs can expose data in plaintextCVE-2026-1280648.5 / 8.4 / 8.3 / 8.2
StandardDenial of service through folded HTTP response headersCVE-2026-1279608.5 / 8.4 / 8.3 / 8.2
URIUpgrade to uriparser 1.0.3CVE-2026-488418.5
URIIncorrect RFC 3986 URI serialization for oversized inputCVE-2026-1294388.5

The two Core entries and the two URI entries appear only in the 8.5 ChangeLog. URI is an extension added in PHP 8.5. Details for each issue are published as GitHub security advisories (GHSA) in php-src; the main ones are listed in the related links.

3. Fixes per branch and support dates

BranchFixed releaseCVEs fixedActive supportSecurity support
8.68.6.0Same fixes2028-12-312030-12-31
8.58.5.13182027-12-312029-12-31
8.48.4.28142026-12-312028-12-31
8.38.3.37132025-12-31 (ended)2027-12-31
8.28.2.36122024-12-31 (ended)2026-12-31
8.1 and earlierNone—EndedEnded (8.1 on 2025-12-31)

Branches with fewer entries presumably do not contain the affected feature or code. Per the ChangeLogs, 8.3 does not include the DOM fix CVE-2026-129501, and 8.2 also does not include the session fix CVE-2026-129481.

PHP 8.2 security support ends on December 31, 2026, at the end of next month. After that, fixes like these will no longer be provided, so plan a move to 8.3 or later if you run 8.2. PHP 8.1 reached end of life on December 31, 2025 (last release 8.1.34) and gets none of these fixes.

4. Setups that are more exposed

Which issues actually affect you depends on the features and setup you use. If any of the following apply, update sooner rather than later.

  • PHP-FPM. Most production setups with Nginx or Apache use PHP-FPM. This release includes three PHP-FPM fixes (epoll use-after-free, request smuggling, and status page XSS).
  • php-cgi. If you run PHP as CGI, the PATH_INFO correction issue (CVE-2026-129538) applies.
  • PHP sessions. Many applications call session_start(), so the session fixes (three on 8.5–8.3, two on 8.2) are relevant.
  • Applications using SOAP, DOM or Phar. For example, integrations with external SOAP APIs, generating or processing XML, or handling signed PHAR files. php -m shows whether these extensions are loaded.

Is your PHP-FPM status page exposed?

CVE-2026-129292 is an XSS in the PHP-FPM status page (pm.status_path). If you have the status page enabled, in addition to updating, restrict access to the clients that need it, such as your monitoring server.

# Is the status page enabled? (paths differ by distribution)
grep -R "pm.status_path" /etc/php-fpm.d/ /etc/php/*/fpm/pool.d/ 2>/dev/null

# Example of restricting access in Nginx
location = /status {
    allow 127.0.0.1;
    deny all;
    include fastcgi_params;
    fastcgi_param SCRIPT_FILENAME $fastcgi_script_name;
    fastcgi_pass unix:/run/php-fpm/www.sock;
}

5. Check your version

# CLI PHP version
php -v

# PHP-FPM version (the command may be php-fpm8.3 etc.)
php-fpm -v

# Loaded extensions (soap / dom / phar / session, etc.)
php -m

# Is php-cgi running?
ps aux | grep [p]hp-cgi

The CLI and the web server may run different PHP builds. Check the web-facing version with the PHP-FPM version or a temporary phpinfo() page, and delete that file afterwards.

8.5.13 / 8.4.28 / 8.3.37 / 8.2.36 or later contain the fixes. Distribution packages may backport fixes without changing the version number; in that case, check the package version against the distribution's security notices.

6. How to update

Whatever method you use, restart PHP-FPM (or Apache) after updating. Otherwise the old PHP processes keep running.

Amazon Linux 2023

The Amazon Linux Security Center shows package status per CVE. Amazon Linux 2023 locks its repositories to the AMI release, so use --releasever=latest to check and update.

# Check for a security update by CVE
sudo dnf updateinfo list --cve CVE-2026-115560 --releasever=latest

# Update the PHP packages from the latest release (adjust for php8.4 etc.)
sudo dnf upgrade --releasever=latest 'php8.3*'

# Restart and verify
sudo systemctl restart php-fpm
php -v

Ubuntu / Debian

If you use the distribution's own packages, check its security notices for the fix. If you use the ondrej/php PPA (Ubuntu) or packages.sury.org (Debian), check whether the new versions are available there.

# Installed PHP packages
apt list --installed 'php*'

# Update only the PHP packages (8.3 example)
sudo apt update
sudo apt install --only-upgrade 'php8.3*'

# Restart and verify
sudo systemctl restart php8.3-fpm
php -v

Docker (official images)

If you use an official image such as php:8.x-fpm, pull the image with the fixed PHP, rebuild your application image and redeploy. Updating inside a running container is undone by the next deployment.

# Re-pull the base image and build (Dockerfile FROM php:8.3-fpm)
docker build --pull -t myapp:latest .

# Check the PHP version in the image
docker run --rm myapp:latest php -v

If you pin the patch version, as in FROM php:8.3.36-fpm, change the tag before building. On ECS and similar services, replace the tasks with the new image.

Managed hosting

On managed WordPress hosts (Kinsta, for example), PHP updates are normally applied by the host at the platform level. Check your host's announcements for status.

FAQ

Frequently Asked Questions

QI already applied the October php2shell update (8.5.12 / 8.4.27 / 8.3.36 / 8.2.35). Do I need to update again?
A

Yes. The vulnerabilities fixed this time are different from October's and are not included in 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35. Update to 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36 or later.

QDo I need to move to PHP 8.6?
A

For the security fixes alone, updating to the fixed release of the branch you already use is enough. 8.6.0 contains the same fixes, but it is a new minor version, so you would need to check application compatibility.

QWhat if I am on PHP 8.1 or earlier?
A

PHP 8.1 reached end of life on December 31, 2025 (the last release was 8.1.34) and does not receive these fixes. Plan a move to a supported branch. PHP 8.2 security support also ends on December 31, 2026, so we recommend planning a move to 8.3 or later.

QI updated on Ubuntu / Debian, but php -v does not show 8.x.37 or similar.
A

Distribution packages sometimes backport fixes without changing the version number. In that case, check the package version against your distribution's security notices to confirm the CVEs are fixed.

QI use managed WordPress hosting. Do I need to do anything?
A

On managed hosts such as Kinsta, PHP updates are normally applied by the host at the platform level. Check your host's announcements for status, and if you can choose the PHP version, pick a supported one.

MOOBONISO/IEC 27001 CertificationAWS Partner Select Tier ServicesKinsta Agency Partner Badge
Copyright © 2026 MOOBON, Inc. All Rights Reserved.
Standard: ISO/IEC 27001:2022
Scope: Web system design support / Development, operation, and maintenance of in-house cloud services / Contract system development, operation, and maintenance / Server construction, operation, and maintenance