CVE-2026-109618: PHP remote code execution through out-of-memory handling

Data Security

CVE-2026-109618 is a critical flaw in the way PHP aborts a request that runs out of memory. A remote attacker who can push a request into that state can end up running code on the server. It was published on October 21, 2026, and Opensolr was patched against it that same day.

01 · At a glance

Identifier
CVE-2026-109618
Severity
9.2 Critical (CVSS v4.0)
Published
October 21, 2026
Fixed in
PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12
Released with
CVE-2026-109619, fixed in the same PHP releases
Opensolr
Patched on October 21, 2026
Last reviewed
November 20, 2026

02 · What it is

When PHP cannot allocate memory it jumps straight out of the code that was running and aborts the request. Some parts of PHP do not account for being interrupted like that and leave request memory in an uninitialized state just before an allocation.

The cleanup that follows can read or branch on that memory. Several ways of forcing an out-of-memory error reach this state reliably, and the result can be remote code execution.

03 · Who is affected

  • Every PHP site on a release older than the fixed ones, in any SAPI that serves network requests: PHP-FPM, mod_php, CGI.
  • No special setting is needed. A request that makes PHP hit its memory limit is enough to reach the vulnerable path.

04 · How to fix it

Upgrade to PHP 8.2.35, 8.3.36, 8.4.27 or 8.5.12, or any later release of your branch, and restart PHP-FPM or the web server.

php -v
sudo apt update && sudo apt install --only-upgrade 'php8.*'
sudo systemctl restart php8.4-fpm

PHP branches that have reached end of life receive the fix only through the extended security maintenance of the operating system vendor.

05 · How to mitigate until you can upgrade

These settings narrow the ways a request can drive PHP into its memory limit. They reduce exposure and do not replace the upgrade.

max_multipart_body_parts = 1000
max_input_vars = 1000
post_max_size = 16M
upload_max_filesize = 16M

Choose limits your application can live with. A web application firewall or a reverse proxy that caps request body size and field count adds a second layer.

06 · How to check a server

php-fpm8.4 -v | head -1
php-fpm8.4 -i | grep -E '^(memory_limit|max_multipart_body_parts|max_input_vars|post_max_size)'
grep -c 'Allowed memory size' /var/log/php8.4-fpm.log

07 · Opensolr and this vulnerability

Status on November 20, 2026. Opensolr is patched against CVE-2026-109618. The fixed PHP releases were installed on October 21, 2026, the day they were published. Nothing is required from you: your Opensolr Index, your account and your data are not exposed to it.

  • Opensolr watches newly published vulnerabilities for every component of the platform, around the clock.
  • Each advisory is assessed against the platform as soon as it is published.
  • The fix is applied, or the vulnerable condition is closed, and the result is verified before the case is closed.

More on how Opensolr protects your data: Opensolr Trust Center and all security pages. Questions about a vulnerability that is not listed: contact Opensolr.

Official advisory: PHP security advisory GHSA-w8hw-w9fx-j79w · NVD entry.