deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

PHP and Node.js ship same-day patches for critical remote code execution flaws

PHP's PHP2Shell bugs and a Node.js Brotli decoder flaw, all scored 9.2 under CVSS v4.0, were patched on October 21, 2026, and exploitation attempts were reported within hours.

PHP and Node.js ship same-day patches for critical remote code execution flaws

What happened

On October 21, 2026, PHP and Node.js both pushed out urgent security releases on the same day. According to a patch guide published on dev.to, the PHP updates close two critical vulnerabilities nicknamed PHP2Shell — CVE-2026-109618 and CVE-2026-109619 — while the Node.js release fixes an out-of-bounds write in its built-in Brotli decompressor, CVE-2026-111497. All three carry a CVSS v4.0 score of 9.2 and can be abused for unauthenticated remote code execution.

The remedy is simple: update, then restart. Fixed versions are PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 and later, and Node.js 22.23.4, 24.22.1 or 26.12.1 and later. A process still running the old interpreter in memory stays vulnerable even after the new version is installed on disk, so every PHP worker and Node process needs a restart.

PHP2Shell, in plain terms

PHP2Shell is the label for two memory-handling mistakes in the PHP runtime itself, not in WordPress, Laravel or any plugin. That distinction matters: updating an application or its extensions achieves nothing, because the engine underneath has to be replaced.

dev.to breaks the bugs down as follows. In CVE-2026-109618, PHP can abort while still setting up a request when memory runs out at the wrong moment, and the cleanup routine then treats half-built data as valid. In CVE-2026-109619, internal data belonging to a request survives after its memory has been freed, and the interpreter may use it again later. Both belong to the class of bug that attackers have historically escalated into code execution.

Who is affected

Almost every PHP version back to 5.4 is exposed, across the common ways of running PHP: Apache mod_php, PHP-FPM, php-cgi, FrankenPHP and LiteSpeed. dev.to flags mod_php as the highest-risk setup because a single request can trigger the flaw before any application code runs. Researchers also noted that an attacker may be able to read memory from a live PHP worker, which can hold passwords, API keys and session tokens — so even a failed attempt can leak data.

The PHP project's advisory states there are no complete mitigations and updating is the only safe choice. PHP 8.1 and older are end-of-life with no official fix, and PHP 8.2 expires on December 31, 2026. One practical wrinkle: Linux distributions often backport the fix while keeping an older-looking version number, so operators should search package changelogs for the CVE identifiers rather than trusting version comparisons alone.

Exploitation has started

Details leaked a day before the planned disclosure. According to dev.to, security firm watchTowr reported active exploitation attempts against both PHP flaws within hours of the patches going out, and Cloudflare said it had observed early attacks and deployed firewall rules in response. No publicly confirmed successful break-in had been documented at the time of writing.

The Node.js side

CVE-2026-111497 sits in the Brotli decoder inside Node's zlib module. A malformed Brotli stream can make it write outside its allotted memory, which can crash an application, leak memory, or lead to remote code execution; Node.js rates it High. The biggest exposure is code that decompresses Brotli data from others: HTTP clients and proxies accepting Content-Encoding: br responses from servers they do not control, APIs taking compressed request bodies, and services handling uploaded compressed files.

The same release addressed ten CVEs in total. Notable companions include three TLS certificate verification bypasses triggered by unusual IP address encodings such as fullwidth digits or leading zeros (CVE-2026-105483, CVE-2026-106069, CVE-2026-106072); dns.resolve() and dns.reverse() silently truncating hostnames at hidden NUL characters (CVE-2026-105482); a malicious server desynchronising keep-alive connections so an early response gets attributed to the next request (CVE-2026-105481); and single-executable or snapshot-built apps generating identical crypto.randomUUID() values across processes (CVE-2026-106074).

Odd-numbered lines (25, 23, 21) and Node.js 20 or older received no fix, so those users must move to 22, 24 or 26 — with 26 becoming the active LTS line on October 28, 2026.

A third PHP flaw, still open

Two days after the release, PHP published an informational advisory about CVE-2026-115560, a separate remote code execution risk in the session upload progress feature that, as of November 7, 2026, has no released fix. The conditions are narrow — a specific session serializer setting, an ini_set() switch before the session starts, and upload progress enabled — but PHP's own recommendation is to disable the feature by setting session.upload_progress.enabled = 0 and restarting. Normal file uploads keep working; only built-in progress tracking is lost.

The Brotli bug also reached into PHP: official Windows builds bundle the Brotli library, so PHP shipped rebuilt Windows packages on October 26.

Why it matters

These flaws live in the runtimes beneath entire ecosystems, so a large share of the web — WordPress sites, Laravel apps, purchased PHP scripts and anything built on Node.js — inherits them regardless of how well maintained the application itself is. There is no configuration workaround for the PHP bugs, exploitation attempts were observed within hours of disclosure, and a patched binary on disk still leaves a server exposed until processes restart. Teams on unsupported lines get no fix at all, turning this from a routine patch into a forced migration deadline for anyone still running legacy PHP or old Node.

  • #php
  • #node-js
  • #security
  • #remote-code-execution
  • #patching

Related posts