The PHP team released PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November 2026, a security update that fixes 17 vulnerabilities. Seven are rated critical in the project’s advisories, and several can lead to remote code execution. The PHP security team notes that the critical issues require non-default configuration or uncommon setups, but it strongly encourages users to upgrade promptly.
Key points of the PHP security update in 20 seconds
- Fixed versions: 8.5.13, 8.4.28, 8.3.37 and 8.2.36.
- 17 CVEs in the 8.5 branch: seven critical, four high, six moderate.
- Critical flaws hit sessions, PHP-FPM, the Date extension and the core.
- PHP 8.2 security support ends on 31 December 2026.
As Administración de Sistemas reports, the release was announced a day in advance. On 18 November the PHP security team said on php.net that releases for all supported branches would ship the next day between 14:00 and 14:30 UTC, that the highest severity was critical, and that users should prepare to upgrade. The update is part of PHP’s regular four-week release cycle. PHP 8.6.0, the next major version of the language, was released the same day.
It also lands in a busy season for PHP. In October, CISA, the US cybersecurity agency, urged organizations to patch the flaws known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619), which allowed unauthenticated code execution. For administrators, that means a PHP update applied a month ago is not enough: every server needs another pass.
All 17 CVEs
This is the full list of vulnerabilities fixed in PHP 8.5.13, with the severity assigned in each php-src security advisory and the branches where each fix appears in the official changelog. Older branches do not include fixes for code that does not exist in them, such as the URI extension introduced in PHP 8.5.
| CVE | Advisory | Component | Issue | Severity | Branches |
|---|---|---|---|---|---|
| CVE-2026-115560 | GHSA-658j-r8rw-q6mx | Session | Session serializer mismatch can lead to remote code execution | Critical | 8.2 to 8.5 |
| CVE-2026-126714 | GHSA-fm2m-fjf5-v3cp | Session | Partially overwritten session files can lead to remote code execution | Critical | 8.2 to 8.5 |
| CVE-2026-129481 | GHSA-g3vh-838c-65v7 | Session | Use-after-free after interrupted session shutdown | Critical | 8.3 to 8.5 |
| CVE-2026-129496 | GHSA-gr4f-wgx5-jpfv | Date | Timezone cache use-after-free can lead to remote code execution | Critical | 8.2 to 8.5 |
| CVE-2026-129289 | GHSA-qc49-hpvq-g2w6 | FPM | PHP-FPM request smuggling through an unread HTTP request body | Critical | 8.2 to 8.5 |
| CVE-2026-129474 | GHSA-8mjj-2r7p-4hg2 | Core | Use-after-free in magic method backtraces can lead to remote code execution | Critical | 8.5 only |
| CVE-2026-129182 | GHSA-2fjv-p558-g82m | Core | Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown | Critical | 8.5 only |
| CVE-2026-129291 | GHSA-jm4m-qfqx-967m | FPM | PHP-FPM epoll use-after-free can lead to local privilege escalation | High | 8.2 to 8.5 |
| CVE-2026-128090 | GHSA-68fq-fh7h-f8gr | Phar | PHAR OpenSSL signature bypass via algorithm downgrade | High | 8.2 to 8.5 |
| CVE-2026-128064 | GHSA-f6gg-rchx-xw8j | Standard | Mixed-case HTTPS and FTPS URLs can expose data in plaintext | High | 8.2 to 8.5 |
| CVE-2026-127960 | GHSA-mmf9-xm3v-hg2x | Standard | Denial of service through folded HTTP response headers | High | 8.2 to 8.5 |
| CVE-2026-129538 | GHSA-5j3f-64r7-f564 | CGI | PHP-CGI out-of-bounds read and write during PATH_INFO correction | Moderate | 8.2 to 8.5 |
| CVE-2026-129292 | GHSA-3mg3-cr28-46gc | FPM | PHP-FPM status endpoint XSS via unescaped user and script fields | Moderate | 8.2 to 8.5 |
| CVE-2026-129506 | GHSA-4646-p932-gw34 | SOAP | SOAP use-after-free when processing DTD entity references | Moderate | 8.2 to 8.5 |
| CVE-2026-15353 | GHSA-q23r-hr55-xmpg | SOAP | SOAP information disclosure through malformed array dimensions | Moderate | 8.2 to 8.5 |
| CVE-2026-129501 | GHSA-x8r7-mg3g-74hg | DOM | Double free during DOM XML serialization | Moderate | 8.4 and 8.5 |
| CVE-2026-129438 | GHSA-mg3p-mxj9-g2mm | URI | Incorrect RFC 3986 URI serialization for oversized input | Moderate | 8.5 only |
In practice, PHP 8.5.13 fixes all 17 issues, PHP 8.4.28 fixes 14, PHP 8.3.37 fixes 13 and PHP 8.2.36 fixes 12, according to the official changelog.
Where the risk is for a web server
Three of the critical flaws are in session handling, which almost every PHP application with a login relies on. CVE-2026-115560 involves a mismatch between the serializers used to write and read session data, CVE-2026-126714 involves partially overwritten session files, and CVE-2026-129481 is a use-after-free when session shutdown is interrupted. According to their advisories, the first two can lead to remote code execution.
Cybersecurity News links CVE-2026-115560 to the session upload progress feature and mentions disabling it with session.upload_progress.enabled=0 in php.ini as a temporary mitigation, noting that applications that never change how PHP stores session data at runtime can leave it enabled. Either way, the real fix is upgrading.
PHP-FPM, the process manager behind most Nginx deployments, has three fixes: critical request smuggling (CVE-2026-129289) when an HTTP request body is left unread, a high-severity local privilege escalation (CVE-2026-129291) and a moderate XSS in the status page (CVE-2026-129292). The last one is another reason never to expose pm.status_path to the Internet. The remaining critical issues are a timezone cache use-after-free in the Date extension and two core flaws that only affect PHP 8.5.
Among the high-severity issues, CVE-2026-128064 means mixed-case HTTPS or FTPS URLs can end up sending data in plaintext, and CVE-2026-128090 allows bypassing PHAR OpenSSL signature verification through an algorithm downgrade, which matters where those signatures are trusted to distribute tools.
How to check and update your servers
Start by confirming which version is actually running, which may differ from the installed package if PHP-FPM has not been restarted:
php -v
php-fpm8.3 -v
php -i | grep -i session.upload_progress
systemctl status php8.3-fpm
Adjust the PHP-FPM version to your installation. Then update from your package sources. Distributions often ship fixes with some delay and sometimes backport them without changing the minor version number, so check their security advisories. After updating, restart PHP-FPM or the web server that loads PHP as a module, and verify the running version again, for example with an internal diagnostics page that is not publicly reachable.
If you still run PHP 8.2, this is one of its last updates: the branch stops receiving security fixes on 31 December 2026. PHP 8.1 and older no longer receive any, so they remain exposed unless your distribution maintains its own patches. It is a good time to plan the move to 8.4 or 8.5.
FAQ
Which PHP versions fix these vulnerabilities?
PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, released on 19 November 2026.
How many vulnerabilities are critical?
Seven of the 17 fixed in PHP 8.5.13, according to the project’s advisories. PHP says they require non-default configuration or uncommon setups.
Is there a mitigation if I cannot update yet?
For CVE-2026-115560, Cybersecurity News mentions disabling session.upload_progress.enabled. For the rest, the fix is to upgrade.
When does PHP 8.2 support end?
It receives security fixes until 31 December 2026.
Sources:
