November 20, 2026

PHP’s November Security Release on One Page: Seven Critical Flaws, the Settings That Decide Your Risk, and an Update Checklist

PHP has shipped 8.2.36, 8.3.37, 8.4.28, 8.5.13 and the new 8.6.0 with fixes for seven critical flaws, including the session bug researchers call phpAfterShell. Most need specific configurations, so here is a spec sheet of what changed and a checklist for working out how exposed your sites are.

Macro close-up of a green circuit board with processor chips, capacitors and copper traces

A month after the PHP2Shell scramble, the PHP project is back with another set of critical fixes. This time the maintainers say the seven most serious issues need either non-default configuration or uncommon setups, which makes the job less about panic and more about knowing how your own servers are built. This spec sheet draws on Dark Reading’s analysis and The Hacker News’ breakdown of the individual flaws.

The release at a glance

  • Published: November 19, 2026, as PHP’s monthly security release.
  • Fixed versions: 8.2.36, 8.3.37, 8.4.28 and 8.5.13. PHP 8.6.0, the new major release, launched the same day with the fixes included.
  • Affected: all supported PHP branches, under specific conditions.
  • Critical issues: seven, each rated 9.2. The Hacker News also lists an 8.8-rated local privilege escalation in PHP-FPM.
  • Possible impact: remote code execution, session corruption, memory corruption, crashes and local privilege escalation.
  • Workarounds: included in most of the critical advisories (not for CVE-2026-115560), but described as temporary until you upgrade.

The flaws experts flag first

  • CVE-2026-129289, PHP-FPM request smuggling. Upwind calls this the one to close first, because a single request can give an unauthenticated attacker code execution. It requires a front end that reuses FastCGI connections, such as nginx with fastcgi_keep_conn on or Apache mod_proxy_fcgi with enablereuse=on, plus an application path that opens php://input without reading it to the end.
  • CVE-2026-126714, “phpAfterShell.” Named by Depthfirst, this race in the file-based session handler can leave a session file stitched together from new and old data. When the application later calls session_start(), PHP can deserialize attacker-planted objects, which researchers chained to code execution. It applies to applications using file-based sessions; the suggested stopgap is turning off session upload progress.
  • CVE-2026-115560, session serializer mismatch. An input validation flaw that can lead to code execution. WatchTowr expects attackers to focus on this one, phpAfterShell and the FPM bug first.

The flaws tied to last month’s fixes

  • CVE-2026-129481 (session cleanup use-after-free) and CVE-2026-129182 (fatal error backtrace use-after-free) cover cases that the October fix for PHP2Shell did not, according to Upwind.
  • CVE-2026-129474 (magic method backtrace use-after-free) became remotely reachable through a change in 8.5.12.
  • CVE-2026-129474 and CVE-2026-129182 apply only to PHP 8.5. CVE-2026-129481 does not affect 8.2.
  • CVE-2026-129496, a use-after-free in the timezone cache, can let an unauthenticated remote attacker crash PHP workers or run code.

Your update checklist

  1. Find every place PHP runs. Arctic Wolf warns that many organizations lack a full inventory. Look beyond your main website to content management systems, hosting control panels, vendor appliances, internal tools and container images.
  2. Note how each one runs PHP. PHP-FPM, Apache mod_php and php-cgi carry different risks. Check whether your web server or load balancer reuses FastCGI connections.
  3. Check session settings. Are sessions stored as files, and is session upload progress turned on?
  4. Check the version line. Systems on 8.5 are exposed to the most issues in this batch, since several flaws exist only there.
  5. Upgrade internet-facing systems first to the fixed build for their branch, then internal ones.
  6. Rebuild bundled PHP. Upwind notes that container images and appliances shipping their own PHP need a rebuild or a vendor update.
  7. Use workarounds only as a bridge where an upgrade must wait, and record a date to remove them.

What this means for your company

If your website, customer portal or line-of-business app is built on PHP, this update belongs on this week’s maintenance list even if your configuration turns out not to be exposed. Ask your web host, developers or software vendors directly which PHP version they run and when they will apply the fix, rather than assuming it happens automatically. Use this release to build the PHP inventory you will need next time, including who owns each system. And keep the habit WatchTowr recommends: check how a critical bug is exploited and whether your setup meets the conditions, so urgent patches go first and nothing important gets left behind.

If you are not sure where PHP is running in your business or who is keeping it patched, we can help you find it and set up a routine. Reach out to Layer 7 Data Solutions to discuss how we’ve helped companies similar to yours.

About The Author