1. Overview of the release
| Date | What happened |
|---|---|
| 2026-11-18 | php.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-19 | PHP 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.
| Area | Issue | CVE | Branches |
|---|---|---|---|
| Core | Use-after-free in magic method backtraces can lead to remote code execution | CVE-2026-129474 | 8.5 |
| Core | Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown | CVE-2026-129182 | 8.5 |
| CGI | PHP-CGI out-of-bounds read and write during PATH_INFO correction | CVE-2026-129538 | 8.5 / 8.4 / 8.3 / 8.2 |
| Date | Timezone cache use-after-free can lead to remote code execution | CVE-2026-129496 | 8.5 / 8.4 / 8.3 / 8.2 |
| DOM | Double free during DOM XML serialization | CVE-2026-129501 | 8.5 / 8.4 |
| FPM | PHP-FPM epoll use-after-free can lead to local privilege escalation | CVE-2026-129291 | 8.5 / 8.4 / 8.3 / 8.2 |
| FPM | PHP-FPM request smuggling through an unread HTTP request body | CVE-2026-129289 | 8.5 / 8.4 / 8.3 / 8.2 |
| FPM | PHP-FPM status endpoint XSS via unescaped user and script fields | CVE-2026-129292 | 8.5 / 8.4 / 8.3 / 8.2 |
| Phar | PHAR OpenSSL signature bypass via algorithm downgrade | CVE-2026-128090 | 8.5 / 8.4 / 8.3 / 8.2 |
| Session | Partially overwritten session files can lead to remote code execution | CVE-2026-126714 | 8.5 / 8.4 / 8.3 / 8.2 |
| Session | Session serializer mismatch can lead to remote code execution | CVE-2026-115560 | 8.5 / 8.4 / 8.3 / 8.2 |
| Session | Use-after-free after interrupted session shutdown | CVE-2026-129481 | 8.5 / 8.4 / 8.3 |
| SOAP | SOAP information disclosure through malformed array dimensions | CVE-2026-15353 | 8.5 / 8.4 / 8.3 / 8.2 |
| SOAP | SOAP use-after-free when processing DTD entity references | CVE-2026-129506 | 8.5 / 8.4 / 8.3 / 8.2 |
| Standard | Mixed-case HTTPS and FTPS URLs can expose data in plaintext | CVE-2026-128064 | 8.5 / 8.4 / 8.3 / 8.2 |
| Standard | Denial of service through folded HTTP response headers | CVE-2026-127960 | 8.5 / 8.4 / 8.3 / 8.2 |
| URI | Upgrade to uriparser 1.0.3 | CVE-2026-48841 | 8.5 |
| URI | Incorrect RFC 3986 URI serialization for oversized input | CVE-2026-129438 | 8.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
| Branch | Fixed release | CVEs fixed | Active support | Security support |
|---|---|---|---|---|
| 8.6 | 8.6.0 | Same fixes | 2028-12-31 | 2030-12-31 |
| 8.5 | 8.5.13 | 18 | 2027-12-31 | 2029-12-31 |
| 8.4 | 8.4.28 | 14 | 2026-12-31 | 2028-12-31 |
| 8.3 | 8.3.37 | 13 | 2025-12-31 (ended) | 2027-12-31 |
| 8.2 | 8.2.36 | 12 | 2024-12-31 (ended) | 2026-12-31 |
| 8.1 and earlier | None | — | Ended | Ended (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.
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 -mshows 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.
Related links
We take care of PHP version inventories, regular updates and migrations off PHP 8.2 through our AWS Operations Service. For AWS security settings, try our free security assessment.
References
- PHP: Hypertext Preprocessor (release announcements)
- PHP 8 ChangeLog
- PHP: Supported Versions
- GHSA-658j-r8rw-q6mx (CVE-2026-115560, session serializer mismatch)
- GHSA-fm2m-fjf5-v3cp (CVE-2026-126714, partially overwritten session files)
- GHSA-5j3f-64r7-f564 (CVE-2026-129538, PHP-CGI PATH_INFO)
- GHSA-jm4m-qfqx-967m (CVE-2026-129291, PHP-FPM epoll)
- GHSA-qc49-hpvq-g2w6 (CVE-2026-129289, PHP-FPM request smuggling)
- GHSA-3mg3-cr28-46gc (CVE-2026-129292, PHP-FPM status page)
- php-src security advisories
- Amazon Linux Security Center
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?
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?
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?
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.
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?
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.
