Not Again... Critical PHP Security Vulnerabilities – Update Your Servers

Well, that didn’t take long. Just as we finished worrying about the critical NGINX vulnerabilities, PHP decided it wanted some attention too.

On November 19, 2026, PHP released security updates fixing up to 18 vulnerabilities, including 6 Critical CVEs with a CVSS score of 9.2. Some could allow unauthenticated attackers to execute code on affected servers. Because apparently, keeping a server online wasn’t exciting enough.

What should you do this time?

  • Update PHP to 8.5.13, 8.4.28, 8.3.37, or 8.2.36, or newer.

  • Run php -v to check your installed version.

  • Restart PHP-FPM and your web server after updating.

  • Check whether FastCGI connection reuse is enabled (fastcgi_keep_conn in NGINX or enablereuse in Apache).

  • If you cannot update immediately, disabling FastCGI connection reuse and session.upload_progress.enabled can help mitigate certain vulnerabilities.

  • PHP 8.1 and older are unsupported, while PHP 8.2 reaches end of life on December 31, 2026.

  • If your Linux distribution backports security patches, check its advisories rather than relying on version numbers alone.

WordPress site owners: Yes, this concerns you too. Especially if you’re running PHP-FPM on your own VPS.

The slightly good news? Most critical issues require uncommon configurations, and no exploitation in the wild was reported at disclosure.

Official security updates: PHP 8 ChangeLog

At this rate, server administration is becoming a full-time job just to keep yesterday’s software secure.

See you at the next critical vulnerability announcement. Hopefully not tomorrow.