Kivorent News

Thursday, November 19, 2026

Tech and AINews

PHP ships fixes for 18 flaws, seven critical, across four supported branches

The PHP project released PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on November 19, fixing 18 vulnerabilities, seven rated critical. Most need a non-default setting, but the update lands on hosts, not in WordPress or Laravel.

Warden, covering security, outages and the rules for tech
, 3 min read

18CVEs fixed in the November 19 PHP releases

What to know

  • PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 shipped just after 14:00 UTC on November 19; PHP 8.1 and older got no fixes.
  • Seven of the flaws carry a critical CVSS 9.2 rating, including session-handling bugs and a PHP-FPM request smuggling flaw.
  • No exploitation in the wild had been reported by the afternoon of November 19, and none of the flaws is in CISA's exploited catalog.

If a server runs PHP, the fix for this week's flaws comes from whoever runs the server. Updating WordPress, a plugin or a Laravel app does nothing here. "None of these are WordPress bugs," Patchstack wrote in its breakdown of the release; the bugs sit in the language runtime underneath.

The PHP project shipped PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 just after 14:00 UTC on Thursday, November 19, according to Precursor Security, which tracked the GitHub advisories as they were posted. Patchstack and Precursor both count 18 CVEs: 17 in PHP's own code and one in the bundled uriparser library. Seven are rated critical at CVSS 9.2. PHP 8.6.0, released the same afternoon, carries the same fixes, Precursor reported. We did not load the release notes on php.net itself; the version numbers here match across all three post-release sources.

What has to be switched on

Nearly every critical bug needs a setting or a setup that not every server has. That is the good news, and also the trap, because one of those settings was on by default until today.

  • Session upload progress. Two critical flaws, CVE-2026-126714 and CVE-2026-115560, run through session.upload_progress, which shipped enabled. Precursor says CVE-2026-126714, which researchers at depthfirst named phpAfterShell, bypasses the fix for October's PHP2Shell bugs and exposes any app on an affected version that uses file-based sessions. The new releases turn the setting off by default, according to Patchstack, but an explicit setting in a config file overrides that.
  • PHP-FPM behind a connection-reusing proxy. CVE-2026-129289 is a request smuggling flaw that needs FastCGI connection reuse at the front end (fastcgi_keep_conn on in NGINX, enablereuse=on in Apache). Patchstack flags it as one WordPress hosts should act on, because WordPress's REST API reads the raw request body on every call.
  • File-based error logs. CVE-2026-129496, a use-after-free in the timezone cache, needs a startup warning written to a file-based error_log. Patchstack rates it unauthenticated.

Two more criticals affect only PHP 8.5, and one, CVE-2026-129481, is an incomplete fix for a bug patched in October, Precursor says.

Exploitation status

No attacks using these flaws had been reported as of the afternoon, and none is in CISA's Known Exploited Vulnerabilities catalog. That gap may not last. Precursor cites Italy's national CSIRT saying a proof of concept for CVE-2026-115560 is already online, and the October PHP2Shell bugs did end up exploited: attackers chained them into the Check Point intrusions we covered last week.

Linux distributions often backport fixes without changing the version number, so a server reporting 8.4.27 may or may not be patched. Precursor said Ubuntu, Debian, Red Hat, SUSE and Amazon Linux packages were still pending late Thursday afternoon UTC. Until a fixed build is in place, the advice from Patchstack, Aikido and Precursor is the same: set session.upload_progress.enabled = 0 in php.ini or the FPM pool, then restart the workers. DEV Community's author found that ini_set() in application code cannot change that setting.

The branch with a deadline

PHP 8.1 and older received nothing, Patchstack notes, because they are past end of life. PHP 8.2 joins them on December 31, 42 days after this release. A server still on 8.2 should get this update and an upgrade plan in the same ticket. For reading the advisories themselves, our guide to how to read a security advisory covers the CVSS and affected-version fields; FPM operators patching this week may also be working through the nginx2root fixes published this week.

Sources

Internet, outages and security

Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.