Updated 19 November 2026, 14:30. PHP has now released the fixes. This page replaces our preliminary advisory from this morning with the fixed version numbers and what each flaw affects, taken from PHP's own advisories.
The PHP security team released fixes for every supported version on 19 November 2026, closing 17 vulnerabilities. Seven are rated critical, four high and six moderate, and the most serious PHP vulnerability needs no login on an affected setup. The fixed versions are PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. If your website runs on PHP, which includes every WordPress site, it needs one of those versions, or a host-supplied equivalent, as soon as it can be applied.
This article explains each PHP vulnerability in plain terms, which setups are most at risk, which versions fix it and what to ask your web company or host. If you are unsure which PHP version your site runs, ask them first.
Each PHP Vulnerability Fixed on 19 November, in Plain Terms
The PHP security team gave a day's notice on 18 November. Its announcement said "the highest severity is CRITICAL" and that the critical issues "require either non-default configuration or uncommon setups". The changelog and PHP's security advisories now give the detail. The critical flaws fall into four groups.
Sessions: three critical flaws
PHP sessions are how many sites remember a visitor between pages, for example a logged-in customer or a shopping basket. Three critical fixes are here:
CVE-2026-115560, "Session serializer mismatch can lead to remote code execution". This is the session upload progress flaw PHP flagged on 23 October. It only applies to sites with an unusual combination of session settings and code (details below).
CVE-2026-126714, "Partially overwritten session files can lead to remote code execution". This one affects PHP's default way of storing sessions in files. An attacker has to influence what is stored in the session, interrupt a write at the right moment, and find suitable code already in the application to abuse.
CVE-2026-129481, "Use-after-free after interrupted session shutdown". PHP 8.3 and later only. PHP says code execution through it "has not been demonstrated".
PHP-FPM request smuggling: critical
CVE-2026-129289 affects PHP-FPM, the way most modern hosting runs PHP behind nginx or Apache. On an affected setup, an attacker with no login can slip a second, hidden request through to PHP and run their own code. It needs a web server that keeps its connection to PHP-FPM open between requests (nginx with fastcgi_keep_conn on, or Apache with enablereuse=on) and site code that opens the raw request body without reading all of it. PHP says standard nginx and Apache setups, which close that connection after each request, "are not affected by the demonstrated PHP-FPM attack".
PHP 8.5 only: two critical flaws
CVE-2026-129474 ("Use-after-free in magic method backtraces can lead to remote code execution") and CVE-2026-129182 only affect PHP 8.5. The first needs two settings, fatal_error_backtraces=1 (on by default in 8.5) and zend.exception_ignore_args=0. PHP notes that its recommended production settings file sets zend.exception_ignore_args=1, which "prevents this attack path". The second is a gap left by October's PHP2Shell fix, and PHP says code execution through it "has not been demonstrated".
Error log timestamps: critical
CVE-2026-129496, "Timezone cache use-after-free can lead to remote code execution", affects every supported version. It needs PHP to log errors to a file, a warning while PHP starts up (often from an old or mistyped setting) and a second warning early in a request. PHP has demonstrated code execution "locally in FPM and Apache mod_php with known addresses and additional configuration assumptions".
The high and moderate fixes
The four high-rated fixes cover a way to make PHP accept a tampered signed Phar archive, HTTPS and FTPS addresses written with a capital S being sent unencrypted by PHP's own download functions, a slow-response attack on those functions, and a way for code already running in PHP-FPM to gain the PHP-FPM master's privileges, which are often root. The six moderate fixes cover SOAP, DOM, PHP-CGI, the PHP-FPM status page and URL handling in PHP 8.5.
None of these is "PHP2Shell" again. Two of the fixes close gaps left by October's PHP2Shell fix, which is another reason to apply this release even if you patched in October.
Is Your Website Affected?
Almost every PHP site is running a vulnerable version until it is updated, but whether a given flaw can actually be used against your site depends on how PHP is set up. That is the part your host or web company has to check. In short:
Sites on PHP 8.5 have the most to fix (all 17). PHP 8.4 has 14 of them, 8.3 has 13 and 8.2 has 12.
Sites on PHP-FPM behind a web server that reuses connections to it are exposed to the request smuggling flaw, which needs no login.
Sites that store user-supplied data in PHP sessions, such as shops and membership sites, are in scope for the session flaws.
Sites whose PHP logs errors to a file and shows startup warnings are in scope for the timezone flaw.
The session upload progress flaw (CVE-2026-115560)
PHP says three things all have to be true for this one:
the site's PHP configuration sets
session.serialize_handlertophp_binaryorphp_serialize;the site's code reads the same session using the default
phpformat, for example by switching the setting back while it runs;session upload progress is still switched on, which is the default.
That combination is rare. PHP rates it critical because of what happens when all three line up.
Does It Affect WordPress Sites?
WordPress runs on PHP, so every WordPress site needs the updated PHP version. WordPress itself doesn't start PHP sessions, which lowers the risk from the session flaws, but some plugins do, and WordPress's Site Health screen warns when a plugin leaves a session open. Updating WordPress and plugins doesn't update PHP: the PHP version on the server is what matters.
Which PHP Versions Fix It
The patched versions are listed in PHP's changelog. Support end dates are from the PHP supported versions page.
| PHP line | Fixed version | Security support ends |
|---|---|---|
| PHP 8.5 | 8.5.13 | 31 December 2029 |
| PHP 8.4 | 8.4.28 | 31 December 2028 |
| PHP 8.3 | 8.3.37 | 31 December 2027 |
| PHP 8.2 | 8.2.36 | 31 December 2026 |
| PHP 8.1 and older | No official fix | End of life |
PHP 8.2 loses security support on 31 December 2026, six weeks from now, so a site on 8.2 needs a move planned even after this update. Our guide to PHP end-of-life dates covers what that involves. Sites on PHP 8.1 or older get no official fix and depend on their host backporting one.
Hosts that install PHP from Linux distribution packages may ship the fixes under their own version numbers. In that case, ask your host for the date the 19 November fixes were applied.
Check Your PHP Version Against the Fixed Releases
Find the PHP version serving your site, then compare it with the table. Your hosting control panel usually shows it under PHP settings, and on WordPress it is under Tools > Site Health > Info > Server. The version that matters is the one handling live web traffic, which can differ from the command-line version, so ask your host to confirm the web-facing one.
If You Can't Update Straight Away
PHP's advice is to update. Its advisories list stopgaps for some of the flaws, each one a setting for your host or developer to change:
Request smuggling: "disable backend connection reuse on the affected front end", for example by leaving nginx
fastcgi_keep_connand Apacheenablereuseswitched off.Session files and upload progress: "disable
session.upload_progress.enabledadministratively if the feature is not needed". If your host did this after PHP2Shell in October, keep it in place. PHP adds that this "does not fix applications that independently store attacker-controlled session data".PHP 8.5 backtraces: "disable fatal-error backtraces administratively with
fatal_error_backtraces=0and restart all workers".Timezone flaw: "correct configuration errors and deprecated settings that produce startup diagnostics, then restart the PHP master process and all workers".
These are stopgaps, not the fix, and they don't cover every flaw in the release.
Is It Being Exploited?
As at 14:30 on 19 November 2026, PHP's advisories don't report any exploitation attempts, and none is on the US cybersecurity agency CISA's list of known exploited vulnerabilities. The full technical details are now public, so attackers can study them too. That is the reason to update promptly rather than wait for reports of attacks.
What to Ask Your Web Company or Host
Which PHP version is serving my live website?
Has it been updated to the 19 November 2026 release (8.5.13, 8.4.28, 8.3.37 or 8.2.36, or your packaged equivalent)?
Does the web server keep its connection to PHP-FPM open between requests?
If my site is on PHP 8.1 or older, is a backported fix available?
If my site is on PHP 8.2, when are we moving to a supported version?
A useful answer gives you a version number and a date.
If Your Site Was Unpatched: Check for Signs of a Hack
Our guide to signs your website has been hacked covers the signs to watch for. If you find something you can't explain, our hacked website recovery service is for sites not on our platform.
Keeping PHP Up to Date Without Chasing It
This is PHP's second critical release in four weeks, after PHP2Shell on 21 October. Each one means applying PHP security updates on the server as well as updating the website. For most small businesses the practical answer is a managed website where that's done for you.
On our platform, security patches and updates are handled as part of your plan, with backups included. Our managed websites page sets out what each plan covers.
FAQs
If you want hosting where PHP updates are handled for you, our managed websites plans set out what's included. Or get in touch to talk through your site.
Is this the same as PHP2Shell?
No. PHP2Shell was two flaws (CVE-2026-109618 and CVE-2026-109619) fixed on 21 October 2026. This is PHP's next regular security release, four weeks later, with 17 fixes. Two of them close gaps left by the PHP2Shell fix.
Which PHP versions fix the 19 November 2026 vulnerabilities?
PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. PHP 8.1 and older get no official fix.
Do I need to update PHP if my WordPress plugins are up to date?
Yes. These are flaws in PHP itself, which runs on the server. Plugin and WordPress updates don't change the PHP version.
Will updating PHP break my website?
A minor update within the same line, such as 8.3.36 to 8.3.37, rarely does. A jump between lines, such as 8.1 to 8.3, carries more risk and should be tested on a staging copy first.
What is CVE-2026-115560?
A critical PHP flaw in session upload progress that could allow remote code execution, but only on sites with an unusual combination of session settings and code. PHP flagged it on 23 October 2026 and fixed it in the 19 November release.
Callum Robley
Founder & Lead Developer, Tea Powered Projects
Callum is a full-stack developer and the founder of Tea Powered Projects, a web design, development, and hosting company based in Nottingham, UK. With over 15 years of industry experience, he specialises in building reliable, scalable digital solutions for businesses of all sizes.