Skip to content
Reachability Analysis

CVE-2026-109618: PHP Group PHP, is it exploitable where you run it

Code called: yesReached: openControl in front: noExploitation known: yesWalk it through the four questions

What the flaw is

PHP leaves a request through longjmp() when it runs out of memory. In some places during request startup, request memory is reachable before it is fully set up. If any allocation fails at that point, PHP skips the cleanup that would reset it, and the request shutdown code later reads or branches on the invalid memory. The failed allocation does not need to be related to the broken memory. CWE-416.

The confirmed result is unauthenticated remote code execution as the web worker account. PHP's advisory says this was validated over HTTP against Apache mod_php with default input and memory limits and normal prefork configurations. Extra workers and unrelated traffic raise the number of attempts needed but do not remove the condition. Several multipart parsing problems let a request reach the out-of-memory state while staying inside its apparent PHP limits. Reliability depends on the PHP build, extensions, frontend and allocator layout.

Ratings: NVD's primary CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N). PHP's own CVSS 4.0 base score, also in NVD, is 9.2 with attack complexity High. CVE-2026-109619 is the sibling flaw from the same release, and PHP says to follow the remediation advice for both.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
Version: the PHP build serving web requests is below 8.2.35, 8.3.36, 8.4.27 or 8.5.12.Run the binary of the web SAPI, not only the CLI: php-fpm -v, php-cgi -v, or for mod_php run php -v and confirm with apachectl -M | grep -i php (Debian and Ubuntu: apache2ctl -M | grep -i php). For packages run rpm -q php or dpkg -l 'php*'. Packages may be patched without a version change, so also run rpm -q --changelog php | grep -i 109618 or apt changelog php8.3 | grep -i 109618. Check every host and every container image, including PHP bundled inside appliances and Docker base images.
A web SAPI is in use: mod_php, PHP-FPM, php-cgi, FrankenPHP or LiteSpeed.Run ps -ef | grep -Ei 'php-fpm|php-cgi|frankenphp|lsphp|httpd|apache2' and apachectl -M | grep -i php. If PHP runs only from the command line for cron jobs, this condition is false for that host.
An unauthenticated client can reach a PHP script and send it a multipart POST.From a host outside your network, send a POST with no credentials to a known PHP entry point such as /index.php and see whether the server hands it to PHP (any PHP response, even an error page, means yes). Review which vhosts and locations pass .php to PHP in the web server configuration (grep -R 'fastcgi_pass|SetHandler|proxy:fcgi|AddHandler' /etc/nginx /etc/apache2 /etc/httpd). A frontend that blocks multipart bodies, or that requires login for every PHP path, removes this condition.
A finite memory_limit applies to the worker that handles the request.Look at the value each SAPI uses, not only the CLI: grep -Rn 'memory_limit' /etc/php* /usr/local/etc/php* /etc/php-fpm.d /etc/apache2 /etc/httpd. Check pool files for php_admin_value[memory_limit] and php_value[memory_limit], Apache php_value / php_admin_value lines, and .htaccess files. A value of -1 means no limit, which reduces the confirmed exploit but does not make the host safe.

Affected and fixed versions

GitHub's advisory and NVD list the four supported branches. CISA tells operators still on PHP 8.1 or older to take PHP-based systems offline until they are patched or updated, and Fastly tells them to ask their package distributor about backports or upgrade. Distribution packages often keep the old version number and add the fix as a backport, so check the package changelog for the CVE ID as well as the version.
PHP branchAffectedFirst fixed release
PHP 8.5Earlier than 8.5.128.5.12
PHP 8.4Earlier than 8.4.278.4.27
PHP 8.3Earlier than 8.3.368.3.36
PHP 8.2Earlier than 8.2.358.2.35
PHP 8.1 and olderUnsupported branches; PHP publishes no fixNone upstream

If the fix cannot go in yet

  • Upgrade to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or to your distribution's patched package. PHP calls this the only complete mitigation. Cost: a PHP restart, and the usual regression testing for a minor release. The patch replaces longjmp() on out-of-memory with a delayed soft failure at the next VM safe point and an immediate hard exit through _exit() at a second, higher memory threshold.
  • If you cannot update: set memory_limit=-1 administratively and restart every PHP worker, then confirm no pool, directory or application setting restores a finite limit. Cost: a runaway script is no longer stopped by PHP and can use all host memory. This is not complete, since a failed mmap() can still hit the vulnerable path.
  • Keep post_max_size conservative and enforce the decoded request size at the frontend. Lower max_input_nesting_level, and bound input variables, multipart parts, headers per part and uploads. Cost: large uploads and deeply nested forms are refused. PHP says these controls reduce out-of-memory and denial of service risk even after patching.
  • If the application does not use multipart form data, block multipart requests at the frontend before they reach PHP. Cost: file uploads and multipart forms stop working.
  • A container or cgroup memory limit (memory.max) can stand in for PHP's own limit, with caveats. It does not guarantee allocation failure is avoided, and killing a whole container or cgroup can kill the FPM master and all workers unless each worker has its own group. Do not use RLIMIT_AS or RLIMIT_DATA as a substitute: they make mmap() fail and trigger the vulnerable path.
  • CISA's guidance for systems that cannot be updated, and for PHP 8.1 and older, is to take them offline until patched. A WAF may give partial protection in the meantime. Fastly's Next-Gen WAF has a CVE-specific rule covering both PHP2Shell CVEs; opt in to it. Cost of blocking IP lists: Fastly warns that several circulating lists include VPN exits, Tor exits and residential addresses carrying ordinary traffic.

What to look for

  • Network indicator (Fastly): the most widespread exploit kit sends POST to /index.php or / with User-Agent php2shell-109618 and Content-Type multipart/form-data with the fixed boundary B7kQpoc618, a fixed-size body and a minimal header set. It targets raw IP addresses and sends one or two requests per host. Fastly says the multipart boundary string is the most reliable separator; User-Agent strings, source IPs and body sizes go stale within a day and mislead.
  • Rule out look-alikes first (Fastly): chunked multipart requests with no Content-Length, and bodies padded with long runs of the letter A, were 98.6% and 99.9% React2Shell (CVE-2025-55182) traffic in the hour Fastly measured. React2Shell requests carry a Next-Action header, which PHP traffic never does. A WordPress kit with a boundary starting ----wp2shell is a separate July 2026 campaign.
  • Host evidence: success is not visible at the edge, so check the origin. Look in PHP-FPM error logs and Apache error logs for worker crashes, for example AH00051 'child pid ... exit signal' entries. Look for unexpected outbound connections from PHP workers, since a connect-back shell is origin egress (Fastly). CISA: monitor for PHP worker processes launching shells or downloading tools.
  • CISA published a SIGMA detection rule for suspicious activity in its alert, updated 23 Oct 2026. Fastly saw no payload string to match, because the exploit is a failure condition. About a third of the PHP2Shell-named traffic Fastly saw labeled itself as authorized exposure or patch-state checking, so scanning volume alone does not equal exploitation.

Exploited on the day of disclosure, 21 Oct 2026.

Exploitation reported so far

Exploitation is public and mass-scale. Fastly reports that tools named after the bug appeared in its WAF telemetry from 21 Oct 2026 at 03:59 UTC, more than nine hours before the coordinated release, and that an exploit kit followed at 05:11 UTC. From the first tool through midday on 22 Oct it stored about 250,000 requests from about 3,200 public IPs. Roughly a third labeled themselves as defensive checks. Fastly counts are lower bounds and cannot show which requests succeeded.

CISA added the CVE to KEV on 26 Oct 2026 and marks forensic triage as required. KEV lists ransomware campaign use as Unknown. The early traffic came before the fixed releases shipped.

Why attack-path analysis settles it

Exposure needs a chain: an unpatched build, a web SAPI, an unauthenticated route to PHP, and a finite memory limit. Tracing that path on each host, rather than reading the 9.8 base score, shows which servers can be hit. Where the path is open, the version check ends the question.

Sources

  1. CVE-2026-109618: NVD record, read 19 Nov 2026
  2. CVE-2026-109618: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
  3. CVE-2026-109618: vendor advisory (PHP GitHub security advisory GHSA-w8hw-w9fx-j79w), read 19 Nov 2026
  4. CVE-2026-109618: Fastly report on PHP2Shell exploitation, disclosure timeline and indicators, read 19 Nov 2026
  5. CVE-2026-109618: CISA alert: Critical Vulnerabilities in PHP Require Immediate Patching, read 19 Nov 2026

Last reviewed 19 Nov 2026.