Emergency PHP Patch: Two Critical CVSS 9.2 RCEs Fixed Across 8.2–8.5Article · digest for October 26
Surreal still life featuring a PHP server, a CVSS 9.2 warning shield, and emergency patch versions for 8.2–8.5.
Article3 sections≈ 4 min

Emergency PHP Patch: Two Critical CVSS 9.2 RCEs Fixed Across 8.2–8.5

If your servers run even a single PHP service—whether it's a corporate portal, an e-commerce store, a Laravel API, or a WordPress monolith—drop what you're doing and check your interpreter version. PHP core maintainers, together with The PHP Foundation, have released a coordinated out-of-band security update across all supported branches: PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35.

The reason for the emergency release is dead serious: it patches two critical unauthenticated remote code execution (RCE) vulnerabilities (CVE-2026-109618 and CVE-2026-109619), both carrying a devastating 9.2 CVSS v4 score.

An attacker needs no credentials, no login, and no access to private admin panels. Sending a specially crafted network request to any public URL on the site is enough to take over the worker process.

Let's look under the hood of the Zend Engine to see how these flaws trigger—and why standard Web Application Firewalls (WAFs) won't save you.

Anatomy of the Flaws: OOM Memory Corruption and Cross-Request Ghosts

Both vulnerabilities sit deep inside the runtime's low-level memory management, though they trigger differently.

The first flaw (CVE-2026-109618) fires when an Out-of-Memory (OOM) error occurs while parsing an incoming HTTP request body (for instance, during a multipart/form-data file upload). At that moment, the Zend Engine invokes its emergency handler via longjmp(), abruptly bypassing normal destructor chains. Internal hash tables and buffers are left half-initialized. On subsequent access, the runtime reads garbage bytes as valid object pointers, letting an attacker overwrite instruction addresses and execute arbitrary binary code.

The second flaw (CVE-2026-109619) targets long-lived worker processes (worker pooling in PHP-FPM or worker mode in FrankenPHP), where a single process handles hundreds of client requests sequentially. Due to a bug in the context-reset routine (php_request_shutdown), a fatal error in one request leaves global pointers referencing freed memory—a classic Use-After-Free. The attacker's next request can reuse that dangling pointer to corrupt the engine's symbol table.

As we noted in our earlier look at memory exhaustion mechanics in the PHP core, state-management bugs in long-lived workers quickly turn into prime exploit territory.

Highest Risk Zone: Why mod_php Fails Before Your App Starts

Among all deployment setups, security researchers singled out Apache with mod_php as the most exposed configuration.

In mod_php, the exploit triggers while the web server module itself is parsing request headers and parameters—before control ever reaches your application code. No input sanitization, Laravel middleware, or WordPress security plugins even get a chance to run.

Worse, a WAF won't reliably block it: the trigger isn't an obvious SQL injection string or XSS tag, but carefully manipulated chunk sizes and binary header structures.

Update Matrix and the PHP 8.2 End-of-Life Deadline

The patches are already live on the official PHP website and packaged in major Linux repositories (Ondřej Surý's PPA for Ubuntu/Debian, and the Remi repo for RHEL/AlmaLinux/Rocky).

Version matrix:

  • PHP 8.5: patched in 8.5.12;
  • PHP 8.4: patched in 8.4.27;
  • PHP 8.3: patched in 8.3.36;
  • PHP 8.2: patched in 8.2.35.

Pay special attention to PHP 8.2: official security support for this branch ends on December 31, 2026. This is one of the last official binary patches for 8.2, so if your apps are still on it, it's time to accelerate your migration to PHP 8.3 or 8.4.

For older branches (PHP 8.1, 8.0, 7.4), there are no free official patches—those lines are already End-Of-Life (EOL). Protecting them requires paid extended-support subscriptions (such as Ubuntu Pro or Red Hat Enterprise Linux) or backporting the C patches yourself.

One critical reminder: after upgrading packages via apt upgrade or dnf update, make sure you perform a full service restart:

sudo systemctl restart php-fpm

Without restarting the process, the old vulnerable binaries stay loaded in RAM and your server remains exposed. Patch now—don't wait.

Want a deep diveVotes help us choose what to break down in detail. This material has 0 votes.
Sources · 2