Short answer: On November 19, 2026, PHP released 8.2.36, 8.3.37, 8.4.28 and 8.5.13 with fixes for 17 vulnerabilities, seven of them rated critical. The ones that affect the most websites are in PHP-FPM and in PHP’s session handling: a request smuggling bug that can run an attacker’s PHP code through a reused FastCGI connection, two ways to turn session data into code execution, a timezone cache use-after-free reachable with a crafted request, and a PHP-FPM bug that lets code running in a worker take over the process that manages the workers. Every PHP version that serves websites on Hostney now runs a fixed build. PHP 8.1 and older get no official fix, but the security backports community maintainers publish for them cover the twelve fixes that apply to PHP 8.2, and our builds of 7.0 to 8.1 carry them. PHP 5.6 is not covered.
What happened#
PHP’s security team published 17 advisories on November 19 at about 14:05 UTC and released the fixed versions the same day. Seven advisories carry a CVSS v4.0 score of 9.2 (critical), four are rated high and six medium. Not every bug exists in every branch: 8.2.36 fixes 12 of them, 8.3.37 fixes 13, 8.4.28 fixes 14, and 8.5.13 fixes all 17, because three of the bugs are in code that only exists in PHP 8.5.
PHP 8.2 is in its last weeks of security support, which ends on December 31, 2026. PHP 8.1 reached end of life at the end of 2025, and nothing older has been maintained for years. For those branches there is no official release. Remi Collet and Ondřej Surý, who maintain the PHP packages many Red Hat and Debian based servers install, publish security backports for end-of-life branches, and their branches for PHP 7.0 to 8.1 received backports of all twelve fixes that apply to PHP 8.2 by release day. Their PHP 5.6 branch did not.
This is the second large PHP security release in a month. In October, PHP2Shell fixed two critical bugs in PHP’s request handling, and two of November’s advisories describe further ways to reach the stale state that the October fix cleared.
The bugs that affect the most websites#
Request smuggling through a reused FastCGI connection (CVE-2026-129289)#
PHP-FPM receives requests from the web server over FastCGI, and FastCGI lets one connection carry several requests in a row. Before PHP accepts the next request on a connection, it has to read the rest of the previous request’s body or close the connection. PHP got this wrong when a script opened
php://input
, the stream that holds the raw request body, without reading it to the end. PHP treated the open stream as proof that the body had been handled, and left the unread bytes in place.
An attacker can arrange those leftover bytes to form a complete FastCGI request of their own. PHP-FPM then accepts it as the next request, and the web server in front never sees it, so its routing, its access rules and its logs do not apply. The forged request chooses the PHP settings it runs with, and PHP’s advisory shows how that turns into running the attacker’s own PHP code, without memory corruption or any race. The settings it changes can also stay active for later requests on the same worker.
It needs two things. The web server must reuse FastCGI connections, which nginx does with
fastcgi_keep_conn on
and Apache with
enablereuse=on
; both are off by default, and PHP’s advisory says standard configurations that close the connection after each request are not affected by the demonstrated attack. And the application has to open
php://input
without reading it fully, which PHP notes can happen in frameworks that open the input stream before routing or authentication.
Session data turned into code (CVE-2026-115560 and CVE-2026-126714)#
PHP stores a session as serialized data, and reading a session back means unserializing it. When an attacker can make PHP unserialize bytes they chose, an application with a suitable chain of classes (often a library such as Guzzle) can be made to run code. Two of the critical bugs give an attacker that opening.
The serializer mismatch. Session upload progress, a feature that records the state of a running upload in the session, can write attacker-supplied data in one session format while a later request reads the same session in another. Read in the wrong format, part of a session key becomes object data. PHP’s report includes command execution on 8.2.35, 8.3.36, 8.4.27 and 8.5.12. The fix switches session upload progress off by default and refuses changes to session settings at runtime while it is on.
The half-written session file. PHP’s default session handler writes a session into its existing file and did not empty the file before every write. A write that stopped part way left the start of the new session followed by the end of the old one, and a carefully shaped pair can read back as data neither session contained. The fix truncates the file before each write and gives up on the write if it cannot.
A third session bug (CVE-2026-129481) is an incomplete part of October’s fix: a fatal error during session shutdown can leave a pointer behind that the next request on the same worker uses after it was freed. It affects PHP 8.3 and newer.
A timezone cache freed too early (CVE-2026-129496)#
PHP formats timestamps in its error log with the configured timezone, and a warning written to a file error log while PHP starts up can leave a reference to memory that is released when startup ends. A warning early in a later request, such as the one PHP logs when a request has more input variables than
max_input_vars
allows, then reads or writes that freed memory, which may already hold the attacker’s request data. PHP crashed an FPM worker this way with a crafted request, the default
max_input_vars
and ordinary nginx limits, and demonstrated command execution with further, less common settings.
The condition needs a warning at startup that goes to a file error log. Confirmed examples are an invalid
date.timezone
value and a warning caused by session configuration. Newly started and recycled workers are exposed until they finish their first normal request.
From a worker to the process that manages them (CVE-2026-129291)#
PHP-FPM runs a master process that starts and stops the workers, and the master often runs as root. With
catch_workers_output
on, the master watches pipes attached to each worker’s output, and a mistake in how it cleaned those pipes up when a worker exited left it holding a reference to a freed record. An attacker who can already run PHP code in a worker can use that to run commands as the master.
PHP rates it high and calls it local privilege escalation, because the attacker needs to run PHP code first. Where one server runs PHP for many customers, any customer’s code is local code, so on shared hosting this deserves the same attention as the remote bugs.
Two PHP 8.5 backtrace bugs (CVE-2026-129474 and CVE-2026-129182)#
PHP 8.5 added backtraces to fatal error messages, switched on by default. Both critical 8.5-only bugs live there. One collects arguments for a backtrace while PHP is entering a
__call()
or
__callStatic()
method and can pick up values that were already freed; PHP’s demonstration needed
zend.exception_ignore_args=0
, which the production
php.ini
does not use. The other is a follow-up to PHP2Shell: some fatal errors during shutdown can store a new backtrace after the October fix cleared it, and the next request on the worker uses it. Turning fatal error backtraces off blocks both demonstrated paths.
The rest of the list#
| CVE | Component | Rating | What it does | Branches |
|---|---|---|---|---|
| CVE-2026-128064 | Streams | High | An
HTTPS://
or
FTPS://
URL with an uppercase S is fetched without encryption, redirects included | 8.2-8.5 |
| CVE-2026-127960 | Streams | High | A response header folded over many lines makes PHP’s HTTP client use excessive CPU | 8.2-8.5 |
| CVE-2026-128090 | Phar | High | An OpenSSL-signed phar archive can be swapped for one checked with a plain hash instead | 8.2-8.5 |
| CVE-2026-129538 | CGI | Medium | Out-of-bounds read and write while php-cgi corrects
PATH_INFO
| 8.2-8.5 |
| CVE-2026-129292 | FPM | Medium | The FPM status page prints request fields without escaping (cross-site scripting) | 8.2-8.5 |
| CVE-2026-15353 | SOAP | Medium | Information disclosure through a malformed array size in a SOAP message | 8.2-8.5 |
| CVE-2026-129506 | SOAP | Medium | Use-after-free when a SOAP document’s DTD entity references are processed | 8.2-8.5 |
| CVE-2026-129501 | DOM | Medium | Double free while serializing a DOM document as XML | 8.4-8.5 |
| CVE-2026-129438 | URI | Medium | The new URI extension serializes oversized input incorrectly | 8.5 |
The first two affect any site whose code fetches URLs with
file_get_contents()
or
fopen()
: WordPress uses its own HTTP client for most requests, but plugins and custom code often call the stream functions directly.
Which versions are fixed#
| PHP branch | Fixed in | Notes |
|---|---|---|
| 8.5 | 8.5.13 | All 17 fixes |
| 8.4 | 8.4.28 | 14 fixes |
| 8.3 | 8.3.37 | 13 fixes |
| 8.2 | 8.2.36 | 12 fixes; security support ends December 31, 2026 |
| 7.0 to 8.1 | No official release | Community backports of the 12 fixes that apply to 8.2 |
| 5.6 | None | No backport |
What we did on Hostney#
The fixed versions#
PHP on Hostney does not come from the operating system. Every version we offer runs in containers built from PHP’s own releases, so a fix does not wait for Red Hat, AlmaLinux or Rocky Linux to rebuild a package. When the official builds of 8.2.36, 8.3.37, 8.4.28 and 8.5.13 were published, we rebuilt the image for each of those versions and rolled it out to every server. Every PHP worker restarted with it, which also clears anything a long-running worker held from before.
PHP 8.1 and older#
For PHP 7.0 to 8.1, our images are built from PHP’s last release of each branch with the community security backports applied on top, and we rebuilt them with the new backports. Before shipping them, we checked the code each backport adds against PHP’s own fixes for 8.2, built every version and tested it. These builds close the known bugs, but they are not official PHP releases, and they cannot fix what nobody has backported. PHP 5.6 has no backport for this release at all.
If a site still runs anything below 8.2, plan its move. The end-of-life PHP guide covers how to test an upgrade before making it, and with 8.2 itself ending in December, 8.3 or newer is the version to move to.
What was closed before the release#
Several of the attack paths in these advisories were already shut on our servers. Session upload progress has been switched off on every PHP version since October, in a setting a site’s own
php.ini
or
.user.ini
cannot turn back on, so the serializer mismatch had no way in. Fatal error backtraces are switched off on PHP 8.5, which blocks both demonstrated 8.5 backtrace attacks. And our web servers close the FastCGI connection after every request, so the request smuggling attack had no reused connection to ride. None of that replaces the update, and every version got it anyway.
What you should do#
If your sites are on Hostney#
Nothing, unless a site runs PHP 8.1 or older. In that case open the site’s PHP manager in the control panel and switch it to 8.3 or newer, and prioritize any site on PHP 5.6.
If you host somewhere else#
Find out which PHP version each site runs. How to check your PHP version covers the command line and
phpinfo()
, and in WordPress the same information is under Tools > Site Health > Info > Server.
Update to 8.2.36, 8.3.37, 8.4.28, 8.5.13 or later, then restart PHP-FPM or Apache so every worker runs the new code. If PHP comes from your Linux distribution, the version number may not change: Debian, Ubuntu and Red Hat backport fixes into their own packages, so check your distribution’s security tracker for the CVEs above.
If you cannot update right away, these settings close the demonstrated attack paths. Each one has a cost, so remove the ones you do not need once you have patched:
; php.ini, or php_admin_flag / php_admin_value in each PHP-FPM pool
session.upload_progress.enabled = 0
zend.exception_ignore_args = 1
fatal_error_backtraces = 0 ; PHP 8.5 and newer only
; each PHP-FPM pool
catch_workers_output = no
Switching
catch_workers_output
off means anything a script writes to its standard output or error stream outside the response no longer reaches the PHP-FPM log. Errors PHP logs itself through
error_log
are not affected.
Check the web server too. In nginx,
fastcgi_keep_conn
should be absent or
off
in every location that passes requests to PHP, which is the default. In Apache, a
ProxyPass
or
<Proxy>
definition for a FastCGI backend should not set
enablereuse=on
. If your PHP-FPM status page is enabled, make sure only your own monitoring can reach it. What PHP-FPM is and how it works explains pools, workers and the master process if these settings are new to you.
None of these settings fixes every bug in the list. PHP’s advisories name the patched release as the fix.
Why a security plugin does not cover this#
Most of these bugs sit in PHP itself or in PHP-FPM, below any WordPress plugin. A smuggled FastCGI request never passes through the web server’s rules, and the session and timezone bugs are reached while PHP sets up a request, before a security plugin gets control. This is the layer server-level security exists for.
If you think a site was attacked#
Look for files you did not upload, admin users you did not create, and unexpected changes to
.user.ini
or
php.ini
files, since several of these attacks work by changing PHP settings. What to do if your WordPress site was hacked covers the cleanup step by step.
Summary#
PHP’s November 19, 2026 release fixes 17 vulnerabilities in 8.2.36, 8.3.37, 8.4.28 and 8.5.13. The most serious are request smuggling through reused FastCGI connections, two ways to turn session data into code execution, a timezone cache use-after-free, a path from a PHP-FPM worker to its master process, and two PHP 8.5 backtrace bugs that follow up on PHP2Shell. Hostney rebuilt every PHP version from PHP’s own releases and the community backports, rolled the builds out to every server and restarted every PHP worker, and several of the attack paths were already closed by settings in place since October. If a site runs PHP 8.1 or older, move it to 8.3 or newer: the backports narrow the gap, and PHP 5.6 has none.