READ. SCROLL. LISTEN.

Unbiased headlines. Facts, not spin.

Unbiased Headlines is an independently owned news organization. We bring you the facts, not opinions, written fresh from 110+ named sources. Sources linked so you can verify it yourself.

← Back to headlines

PHP Patches 18 Flaws Including Seven Critical RCE Bugs; None Reported Exploited Yet

PHP Patches 18 Flaws Including Seven Critical RCE Bugs; None Reported Exploited Yet
PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on Thursday, Nov. 19, fixing 18 vulnerabilities, seven rated critical at CVSS 9.2. A month ago the PHP2Shell flaws were being attacked in the weeks after disclosure, so the window to patch is the open question. None of the new seven is on CISA's exploited list as of Nov. 19.

A month after PHP shipped emergency fixes for the PHP2Shell flaws (CVE-2026-109618 and CVE-2026-109619), the project is back with another round. Today, Thursday, Nov. 19, the PHP team released its scheduled security update: versions 8.5.13, 8.4.28, 8.3.37 and 8.2.36. PHP 8.6.0 shipped the same day with the fixes already included.

The release fixes 18 vulnerabilities in total. Seven are rated critical, each scoring 9.2 on CVSS v4. They cover session handling, the engine, the date extension and PHP-FPM.

The PHP security team gave a heads-up on Wednesday, Nov. 18, warning that the update would address flaws affecting all supported versions.

The PHP-FPM bug is the most direct route in

CVE-2026-129289 is a request smuggling flaw in PHP-FPM. According to security firm Aikido, it lets an unauthenticated attacker run PHP code remotely on servers that reuse connections to PHP-FPM.

Upwind's analysis calls it the one to close first. It needs no memory corruption, race condition or gadget chain, only a single request. It does require a front end that reuses FastCGI connections and an application path that opens php://input without reading it to the end.

Affected setups include certain nginx, Apache, HAProxy and LSAPI configurations. Standard nginx and Apache setups that do not reuse backend connections are not affected. The bug dates to PHP 5.6.0.

Administrators who cannot patch yet can disable persistent backend connections so each connection closes after one request.

Session bugs and the PHP2Shell leftovers

CVE-2026-126714, nicknamed phpAfterShell, was found by security firm depthfirst, which used frontier AI models tuned for cybersecurity. It was reported to PHP at the end of October.

It sits in the default files session handler. PHP rewrites a session file over the old content without clearing it first. If that write is interrupted, the file can hold the start of the new session and the tail of the old one. On the next session_start(), PHP deserializes that patchwork, and an attacker who has planted the right bytes can summon objects of their choosing.

Depthfirst says any application that stores sessions in files is affected. PHP's position is narrower. The project says the critical issues require non-default configuration or uncommon setups, and for this bug it lists extra conditions: the attacker needs control over part of the session data, a way to interrupt the write at the right moment, and an exploitable gadget in the application.

Upwind found the earlier framing too narrow on a related bug. CVE-2026-115560, the session serializer mismatch PHP disclosed on Oct. 23 with a one-line mitigation and no patch, was described then as a risk mainly for apps that change the serialize handler at runtime. The full advisory says separate apps, FPM pools, vhosts or CLI jobs sharing one session store with different serializers are exposed too. Command execution is documented using Guzzle and Monolog gadget chains, including on the October-patched releases 8.2.35, 8.3.36, 8.4.27 and 8.5.12.

Three of the new fixes trace back to October. CVE-2026-129481 and CVE-2026-129182 cover paths the fix for CVE-2026-109619 missed. CVE-2026-129474, a use-after-free tied to magic method backtraces, became remotely reachable through a change introduced in 8.5.12. For the first two, code execution has not been demonstrated.

The remaining critical bugs are a timezone cache use-after-free (CVE-2026-129496) and further use-after-free flaws in the engine and date extension.

Which branches are hit

Not every bug reaches every branch. PHP 8.2 is affected by four of the seven critical flaws. Versions 8.3 and 8.4 are hit by five. PHP 8.5 is affected by all seven. The changelog lists 12 fixed vulnerabilities in 8.2.36 and 18 in 8.5.13.

PHP says older unsupported releases may also be affected by CVE-2026-115560. End-of-life branches get no upstream fix.

Mitigations only go so far

PHP recommends setting session.upload_progress.enabled=0 and restarting workers. That addresses CVE-2026-115560 and removes one input path for CVE-2026-126714. Upwind notes it does nothing for the four use-after-free bugs, and the FPM flaw needs a different setting.

On Wednesday, F5 issued an out-of-band security update for critical NGINX flaws, some of them found with help from frontier AI. NGINX sits in front of many PHP-FPM deployments, so administrators may be patching both layers this week.

Exploitation status

As of Nov. 19, none of the seven critical bugs is in CISA's Known Exploited Vulnerabilities catalog or reported as exploited in the wild, according to Upwind's analysis.

PHP2Shell followed a different path. CISA has since added both of those flaws to its exploited list. Check Point reported campaigns against its own security gateways dating to Oct. 30. Those attacks involved backdoors and destructive tools aimed at VMware ESXi servers. Attackers also targeted Palo Alto Networks firewalls whose administrative interfaces were exposed to the internet.

Whether attackers move as fast on this batch is unknown. Several of the new bugs need unusual configurations or gadget chains, which narrows the pool of targets. The FPM bug needs only one request on the right setup. The patches are part of PHP's regular four-week release cycle.

Sources used for this briefing

8 links from 8 independent newsrooms (syndicated copies of the same report count once)

These are the sources it draws on, linked so you can verify.

center
The Hacker NewsPHP Fixes 7 Critical Flaws, Including Bugs That Could Allow Remote Code Execution
unknown
BleepingComputerPHP security updates fix 18 flaws, including critical RCE bugs
unknown
Cybersecurity DiveCritical remote code execution flaws found in Nginx web server
unknown
UpwindPHP Critical Vulnerabilities: Affected Versions and Mitigations
unknown
SecurityWeekPHP Patches Seven Critical RCE Vulnerabilities
unknown
IT ConnectPHP Security Update: 7 Critical Flaws Fixed Now
unknown
Infosecurity MagazinePHP Releases Patches to Fix 18 Vulnerabilities
unknown
TechBytesPHP Patches Seven Critical RCE Vulnerabilities