TopSyde
Abstract artwork of a smoky quartz crystal lit with muted gold light on a dark background

PHP's November 19 Security Release Fixes phpAfterShell and Six More Critical Flaws

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix seven critical bugs, phpAfterShell (CVE-2026-126714) among them. Who is really exposed, how to check your PHP build and what to do today.

Colton Joseph

Colton Joseph

Founder & Lead Developer

··10 min read

PHP shipped its scheduled security release on Thursday, November 19, 2026. PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix more than a dozen security bugs, and PHP rates seven of them Critical. The one getting the most attention is phpAfterShell (CVE-2026-126714), a flaw in how PHP writes session files that can end in remote code execution.

This is not a repeat of October's PHP2Shell. PHP says every Critical bug in this release needs a non-default setting or an uncommon setup, and nobody has reported attacks so far. It is still a real fix for real bugs, and patching for PHP2Shell in October does not cover any of them.

The Seven Critical Bugs, in Plain Words

Each one needs something specific to be true before it can be used. That is why PHP calls them Critical and also says most servers won't meet the conditions.

BugWhat has to be trueBranches
phpAfterShell, CVE-2026-126714PHP's default file sessions, attacker-shaped session data, a session write cut off midway and code in the app an attacker can chain8.2 to 8.5
Session serializer mismatch, CVE-2026-115560Session upload progress on, plus two apps or configs on the same session storage using different session serializers8.2 to 8.5
PHP-FPM request smuggling, CVE-2026-129289A web server that keeps its connections to PHP-FPM open between requests (nginx fastcgi_keep_conn on, Apache enablereuse=on), plus a script that leaves the request body unread8.2 to 8.5
Timezone cache, CVE-2026-129496A PHP startup warning written to a log file, then a warning on a worker's first request8.2 to 8.5
Session shutdown, CVE-2026-129481A fatal error inside session shutdown code, then another request on the same worker8.3 to 8.5
Magic method backtraces, CVE-2026-129474zend.exception_ignore_args turned off. PHP's production php.ini turns it on8.5 only
Fatal error backtrace, CVE-2026-129182A fatal error while PHP restores per-folder settings at the end of a request8.5 only

One more, CVE-2026-129291, is rated High. It lets someone who can already run code on the server gain more access through PHP-FPM. The rest of the release fixes less severe bugs in SOAP, DOM, Phar, PHP-CGI and URL handling.

The two session bugs share a way in. Both lean on session upload progress, a PHP feature that was on by default until today. The new builds turn it off unless your config turns it back on.

Is My WordPress Site Exposed?

Probably not by default. But nobody can say for sure without seeing the server's config, and on most hosting you can't see it. That's why the answer is the update, not an audit.

  • WordPress itself doesn't use PHP sessions. Plenty of plugins do, from membership and form plugins to carts, and PHP stores sessions as files by default
  • The attack doesn't need session code on the page it targets. ZEST showed an attacker can send the request to any PHP URL
  • The connection reuse bug depends on the web server. nginx leaves it off by default, and your host decides
  • Two of the seven only affect PHP 8.5

How to Check Your WordPress Site's PHP Version

  1. In wp-admin, go to Tools → Site Health → Info.
  2. Open the Server section.
  3. Read the PHP version line. You need the full number, 8.5.13, 8.4.28, 8.3.37 or 8.2.36 or later on your branch.

Site Health reports the PHP build that is serving your site, which is the one that matters. Over SSH, php -v reports the command-line build, which can differ. And if your host or Linux distribution backports fixes into its own packages, the version number may not change, so ask them by CVE number.

What to Do, in Order

1. Get the patched build onto your server. On shared or managed WordPress hosting, your host controls PHP. Ask when the fixed build reaches your site, then check Site Health instead of assuming. On your own server, install the update, restart PHP-FPM or Apache and confirm the running version. Your Linux distribution may not have fixed packages yet, so check its security notices by CVE number. The official PHP Docker images already have the fixed builds.

2. Can't update today? Turn off session upload progress. Set session.upload_progress.enabled = Off in php.ini or your PHP-FPM pool config, then restart PHP. It removes the easiest way in for both session bugs. WordPress's own media uploader doesn't depend on it.

3. After updating, check nothing switches the old behavior back on. An explicit session.upload_progress.enabled = On anywhere in your config overrides PHP's new default. On PHP 8.5, keep zend.exception_ignore_args = On, as PHP's production config sets it.

4. Ask about FastCGI connection reuse. If your web server keeps connections to PHP-FPM open (fastcgi_keep_conn on in nginx), turn it off until PHP is patched.

5. Don't count on a firewall for this one. Cloudflare's PHP2Shell rule #6 already blocks known attempts at CVE-2026-115560, free plans included. Paid plans have a rule for the request smuggling bug, but it only logs by default. There is no rule for phpAfterShell yet. The update is still the fix.

6. Upgrade anything on PHP 8.1 or older. Those branches get no release. PHP 8.2 reaches end of life on December 31, 2026, so 8.3 or later is the better target. Our PHP version guide for WordPress covers how to move up safely.

One warning carried over from October. Code claiming to "test" for these bugs will circulate, and some of it will be malware aimed at the people who run it. Don't download scripts to check your own server.

How This Compares to PHP2Shell

PHP2Shell (October 21) needed no special setup, leaked a day early and was attacked the same morning. Every unpatched PHP server was exposed.

This release (November 19) fixes bugs that each need particular settings, and no attacks have been reported. That makes it less urgent for most sites. It does not make it optional. Proof-of-concept code is already reported for one bug, and researchers are still publishing.

What TopSyde Is Doing for Our Clients

If TopSyde hosts your site, this is where things stand.

  • Every site we host is running the patched PHP build. It took about four hours from PHP's release. PHP on our platform is built and shipped by Kinsta.
  • We checked every site after it updated. Each one serves the patched build and still loads.
  • TopSyde Sentinel scans every site daily for what an attack leaves behind, from webshells and stray PHP files to rogue plugins and admin accounts.

You don't need to open a ticket or change anything. If you want to talk it through anyway, reply to any of our emails or open a ticket in the portal.

Not hosted with us? Our free scanner checks your site from the outside for signs of an infection. It can't see your PHP version, but it will tell you if something is already wrong. If it finds something, our malware removal service cleans it up. Hosting with us, which covers PHP updates and Sentinel, starts at $59/mo per site, and we move your site for free.

Frequently Asked Questions

What is phpAfterShell?

phpAfterShell is the name depthfirst gave to CVE-2026-126714, a flaw in how PHP writes session files. If a session write is cut off midway, PHP can leave a file that is part new data and part old, and reading it back can hand an attacker control. PHP rates it 9.2 under CVSS v4.0 and fixed it on November 19, 2026 in PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36.

Is this as serious as PHP2Shell?

For most sites, no. PHP says each Critical bug in this release needs a non-default setting or an uncommon setup, and no attacks have been reported. PHP2Shell needed neither and was attacked the day it was fixed. Update anyway, because you can't easily tell from outside whether your server meets the conditions.

I patched PHP2Shell in October. Am I covered?

No. These are new bugs. The October builds (8.5.12, 8.4.27, 8.3.36 and 8.2.35) don't contain these fixes, and ZEST reproduced code execution on them. You need the November 19 build for your branch.

Can a WordPress security plugin protect me?

No. The bugs are in PHP itself, below WordPress and every plugin. The fix is a PHP update on the server, and the stopgaps are server settings too.

I'm on PHP 8.1 or older. What now?

No release is coming for those branches. Upgrade to a supported branch, ideally PHP 8.3 or newer since 8.2 reaches end of life on December 31, 2026. Until then, turning off session upload progress in php.ini is the most useful thing you can do.

Colton Joseph
Colton Joseph

Founder & Lead Developer

20+ years full-stack development, WordPress, AI tools & agents

Colton is the founder of TopSyde with 20+ years of full-stack development experience spanning WordPress, cloud infrastructure, and AI-powered tooling. He specializes in performance optimization, server architecture, and building AI agents for automated site management.

Related Articles

View all →

Free malware scanner

Check your site for signs of malware.

Paste your URL to check for injected scripts, suspicious redirects and cloaked content. Results on screen and by email, with no signup. This checks public pages. It cannot rule out backdoors in your server files or database.

Free public-page scan. No signup. Results on screen and by email.