Illustration of a server tower with a blue shield and a wrench, circled by an update arrow

PHP 8.6 Is Out With Critical Patches: What to Run

Admin

On November 19, 2026, the PHP team shipped security releases for all four supported branches (8.2.36, 8.3.37, 8.4.28 and 8.5.13) and, one minute later, PHP 8.6.0. Any site built on WordPress, Drupal or other PHP software is affected: the urgent step is the patch for your branch, not the move to 8.6.

What we know

  • The heads-up: on November 18, php.net announced security releases for every supported branch and said the highest severity was "critical". It added that the critical issues require a non-default configuration or uncommon setups.
  • The patches: on November 19 at 14:00 UTC, php.net released PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. Each announcement calls it a security release and asks users of that branch to upgrade.
  • How many flaws: according to the php.net changelog, 8.5.13 fixes 17 issues with their own security advisory; 8.4.28, 14; 8.3.37, 13; and 8.2.36, 12.
  • How serious: of the 17 advisories published that day in PHP's GitHub repository, 7 are labeled "Critical". They cover, among other areas, sessions, date handling, the interpreter core and PHP-FPM, the component many servers use to run PHP. Several advisories mention possible remote code execution.
  • PHP 8.6.0: released at 14:01 UTC the same day. It is a major version with new features for developers, such as partial function application, a clamp() function and a class for time durations.
  • What comes next: php.net's supported-versions table keeps the end of security fixes for PHP 8.2 on December 31, 2026.

What changes and what doesn't

What changes is the number your server should show. A site on PHP 8.3 that doesn't show 8.3.37 or later is missing today's fixes, even though it is "on 8.3".

What doesn't change is the branch you should use. This release doesn't ask you to move to PHP 8.6. WordPress's compatibility table, updated on November 4, goes up to PHP 8.5. Drupal's marks PHP 8.6 as not supported in its released versions and points to an open issue. Moving to 8.6 today means testing something your CMS doesn't yet sign off on.

How to tell if you're affected

You're affected if your site runs on PHP, as almost every WordPress or Drupal site does. Do this today:

  1. Check your exact version. In WordPress: Tools › Site Health › Info › Server. In Drupal: Reports › Status report. Write down the full number, for example 8.3.36.
  2. Compare it with your branch's minimum. PHP 8.2 → 8.2.36; PHP 8.3 → 8.3.37; PHP 8.4 → 8.4.28; PHP 8.5 → 8.5.13. If your number is lower, you're missing the fixes.
  3. On shared hosting, your provider does the update. Ask in writing: "When will you install PHP 8.x.y on my server, and do you run PHP-FPM?" Ask for a date, not "we're on it".
  4. If you run your own server, update within the same branch using your system's or control panel's packages, restart PHP-FPM or the web server, and go back to step 1 to confirm the number.
  5. If you're still on PHP 8.2 or older, today's patch is one of the last for 8.2. Plan the move to 8.3 or 8.4, which your WordPress or Drupal already supports, before December 31. Versions 8.1 and older no longer appear in php.net's supported-versions table.
  6. After the change, check that the site loads, that forms submit and that server errors (5xx) don't climb in Search Console over the following days.

Related: PHP 8.6 RC3 Is Out, PHP 8.2 Ends Dec 31: Check Your Site

Sources

Updates: if WordPress or Drupal add PHP 8.6 to their tables, or php.net publishes new details on these flaws, they will be added here with a link.

Worried about how this affects your website?
We will go over what to change with you. It is a free 30-minute call.