In short
- On 19 November 2026, PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36. They fix 17 security flaws, 7 of them critical, each scored 9.2 out of 10.
- The critical ones need settings that are not the default, or less common setups. Check three first: PHP-FPM behind a server that reuses connections, PHP 8.5 without the production php.ini, and session upload progress.
- It was the third serious alert in three days, after OpenJDK on 17 November and nginx on 18 November. One patch is not enough: servers need a regular patch window and someone watching the alerts. That is our Security Watch.
On 19 November 2026, the PHP team released four security updates at once: 8.5.13, 8.4.28, 8.3.37 and 8.2.36. They close 17 flaws. Seven are rated critical, and the worst can let an attacker run code on a web server.
PHP runs a large share of the web, from WordPress and Laravel sites to admin panels and APIs. If one of your servers runs PHP, this update is for you.
What PHP fixed
PHP announced the release a day in advance, on 18 November, as part of its regular four-week release cycle. The notice also warned that the worst issues were rated critical.
On GitHub, PHP published 17 security advisories for this release: 7 critical, 4 high and 6 medium. Every critical one scores 9.2 out of 10 under CVSS 4.0. The 8.5.13 changelog lists 18 CVEs, because it also updates a bundled library. Older branches fix fewer of them: 14 in 8.4.28, 13 in 8.3.37 and 12 in 8.2.36.
There is one important limit. In PHP's words, “the issues rated CRITICAL require either non-default configuration or uncommon setups.” That is good news, but only if you know how your servers are set up.
The seven critical flaws:
- CVE-2026-129289: request smuggling in PHP-FPM through an unread request body;
- CVE-2026-129474: use-after-free in magic method backtraces, PHP 8.5 only;
- CVE-2026-115560: session serializer mismatch;
- CVE-2026-126714: partly overwritten session files;
- CVE-2026-129481: use-after-free after an interrupted session shutdown;
- CVE-2026-129182: use-after-free in the fatal error backtrace after shutdown;
- CVE-2026-129496: use-after-free in the timezone cache.
The three flaws to check first
CVE-2026-129289, PHP-FPM. It matters when the web server in front of PHP keeps FastCGI connections open and reuses them: fastcgi_keep_conn on in nginx, enablereuse=on in Apache, or HAProxy. Then one crafted form upload can lead to PHP code chosen by the attacker. No login is needed. Connection reuse is not on by default in nginx or Apache, but some setups turn it on for speed.
CVE-2026-129474, PHP 8.5. It needs two settings. Fatal error backtraces must be on, which is the default in PHP 8.5, and zend.exception_ignore_args must be off. The production php.ini turns that setting on and blocks the attack. The official Docker images for PHP ship the php.ini templates but no active php.ini, so a container that never copied the production file runs without it. The attack is rated hard and depends on the application.
CVE-2026-115560, sessions. It needs session upload progress, which PHP had on by default, and an application that reads and writes sessions in different formats. The fix turns upload progress off by default.
Is your server affected
Any PHP older than 8.5.13, 8.4.28, 8.3.37 or 8.2.36 has at least some of these flaws. PHP 8.1 and older reached end of life, with 8.1 on 31 December 2025, and get no fixes from PHP. PHP 8.2 gets security fixes only until 31 December 2026.
Some Linux distributions still patch their own older packages, for example PHP 8.1 on Ubuntu 22.04. Others ship the fix without changing the version number. On Ubuntu 24.04 the fixed package is 8.3.6-0ubuntu0.24.04.14, so php -v still shows 8.3.6. Debian moved to the new versions, 8.2.36 and 8.4.28.
So php -v alone does not tell you whether you are safe. Check the package version, for example with dpkg -l | grep php, against your distribution's security notice.
Containers need their own check. The official PHP images are already on the new versions, but your running containers are not updated until you rebuild the images and deploy them again.
Not sure which PHP runs on your servers? Let us check and fix it for you.
Send us your site or server address. We check the PHP version, the package and the settings above, install the fixes and tell you what we found.
What to do today
- Update PHP to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or install the fixed package from your Linux distribution.
- Restart PHP-FPM, or Apache if it runs PHP as a module, so the new code is the one running.
- Check the package version, not only
php -v. - Cannot update today? Turn off FastCGI connection reuse until you can:
fastcgi_keep_conn onin nginx,enablereuse=onin Apache. - On PHP 8.5, use the production php.ini or set
zend.exception_ignore_args = On. In Docker, addRUN mv "$PHP_INI_DIR/php.ini-production" "$PHP_INI_DIR/php.ini"to the Dockerfile. - If your site has no upload progress bar, set
session.upload_progress.enabled = 0. - Rebuild Docker images that ship PHP and deploy them again.
- Plan the move off PHP 8.1 and older now, and off 8.2 before 31 December 2026.
Three alerts in three days
This PHP release did not come alone. On 17 November, the OpenJDK project published fixes for ten flaws in Java. On 18 November, nginx fixed ten flaws, five of them known as nginx2root. On 19 November, it was PHP.
Java, nginx and PHP sit under a large part of the websites, APIs and backends that businesses run. Fixes now come out on a schedule: PHP itself works on a four-week cycle, and any release can carry a critical fix.
Timing matters too. The PHP2Shell flaws, fixed on 21 October, were on CISA's list of exploited vulnerabilities five days later. A server that waits for the next quarterly update stays open for weeks.
That is why one patch is not enough. A server needs a regular patch window, someone who watches the security alerts for its stack, and a fast fix when a critical one comes out.
This is what our Security Watch does. When a critical vulnerability comes out, we check your servers, install the fixes and confirm the hole is closed. After that we keep them up to date, so the next critical fix goes in before it can be used against you.
Let us keep your servers patched.
A monthly patch window, a watch on security alerts for nginx, PHP and Java, a fast fix for critical holes and a monthly report. Send us your site or server address and we start with a check.
FAQ
Which PHP versions fix the November 2026 flaws?
PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, all released on 19 November 2026. PHP 8.1 and older get no fixes from PHP, because they reached end of life.
How serious are they?
PHP published 17 security advisories: 7 critical, 4 high and 6 medium. Every critical one scores 9.2 out of 10 under CVSS 4.0. PHP says the critical ones need settings that are not the default, or setups that are not common.
Is this the same as PHP2Shell?
No. PHP2Shell was two other flaws, fixed on 21 October 2026 and later listed by CISA as used in real attacks. The November flaws are new. As of 20 November, CISA had not listed any of them as exploited.
Why does php -v still show the old version after the update?
Some Linux distributions add the fix to their own package without changing the PHP version number. On Ubuntu 24.04 the fixed package is 8.3.6-0ubuntu0.24.04.14, and php -v still says 8.3.6. Check the package version or your distribution's security notice.
Are Docker images affected?
The official PHP images are already on the new versions, so rebuild your images and deploy them again. These images ship no active php.ini, so also copy php.ini-production in your Dockerfile.
Do I need PHP 8.6 for these fixes?
No. PHP 8.6.0 also came out on 19 November as a new release line. The fixes are in 8.5.13, 8.4.28, 8.3.37 and 8.2.36, so you can stay on your branch.
Sources
- PHP news archive: security release notice (18 November) and releases (19 November 2026)
- PHP 8 ChangeLog: 8.5.13, 8.4.28, 8.3.37 and 8.2.36
- php-src security advisories on GitHub
- GHSA-qc49-hpvq-g2w6: CVE-2026-129289, PHP-FPM request smuggling
- GHSA-8mjj-2r7p-4hg2: CVE-2026-129474, use-after-free in magic method backtraces
- GHSA-658j-r8rw-q6mx: CVE-2026-115560, session serializer mismatch
- PHP supported versions
- Ubuntu: CVE-2026-129289
- Debian security tracker: CVE-2026-129289
- Docker official image for PHP: configuration
- CISA Known Exploited Vulnerabilities Catalog
- OpenJDK Vulnerability Advisory, 17 November 2026
- nginx security advisories
