PHP2Shell refers to CVE-2026-109618 and CVE-2026-109619, two vulnerabilities affecting PHP’s multipart request and session upload-progress handling. Under specific runtime conditions, their exploitation can lead to memory corruption, use-after-free and pre-authentication remote code execution.

The decisive factor is the exact runtime build and configuration. The PHP version alone is not enough to determine whether a server is exp†loitable. Our work uses one experimental driver with separate profiles containing the exact binary hash, symbol offsets, pointer ranges and heap-calibration values. All testing takes place in authorized, disposable local labs.

Verified RCE coverage

Our current research matrix contains 42 binary-verified x86_64 RCE profiles covering 42 of 110 supported vulnerable PHP releases, corresponding to 38.2% coverage. Each profile has independent command-output evidence.

PHP branch

Supported vulnerable releases

Verified RCE

Without verified RCE

Coverage

8.2.0–8.2.34

35

7

28

20.0%

8.3.0–8.3.35

36

15

21

41.7%

8.4.0–8.4.26

27

20

7

74.1%

8.5.0–8.5.11

12

0

12

0%

Total

110

42

68

38.2%

Of the 42 normal profiles, 41 were also reproduced after a fresh container restart with a changed ASLR layout. The remaining PHP 8.4.26 profile has independent command-output proof and is pending fresh-ASLR reproduction.

The remaining 68 releases break down as follows:

  • Seven releases, PHP 8.4.1 through 8.4.7, currently have disclosure-only results.

  • 61 releases do not yet have a complete verified RCE chain.

    In several cases, the available results consist only of failed baselines or incomplete calibration.

These results do not prove that the remaining builds are not exploitable. They show that reliable, build-specific exploitation has not yet been completed and independently verified.

Special-case experimental profiles

We maintain three additional experimental profiles separately from the normal 42/110 coverage figure:

Special case

Result

Limitation

PHP 8.2.11

RCE

ASLR disabled

PHP-FPM 8.3.22

RCE

Instrumented, single-worker, direct FastCGI setup

PHP 8.4.26 aarch64

RCE

Exact-build dedicated profile

Including these cases, there are 45 experimental profiles in total. They must not be presented as 45/110 normal coverage because their conditions or architecture differ from the standard x86_64 research matrix.

What the results demonstrate

Across the verified RCE profiles, successful testing included:

  • Actual remote command execution, not only a worker crash.

  • Independent retrieval of command output over HTTP.

  • Exact binary matching and build-specific calibration.

  • Execution in the context of the PHP web worker.

  • Fresh-container reproduction with a changed ASLR layout for 41 of the 42 normal profiles.

These results prove exploitation against the specific tested builds and conditions. They do not establish universal exploitation of every server running the same PHP version.

A crash-only detection result does not prove RCE. Likewise, a profile developed for one binary must not be presented as working on another binary without appropriate testing.

Why there is no universal exploit

A reliable PHP2Shell exploit must resolve build-specific symbols, account for ASLR, identify the relevant heap layout and calibrate several allocation stages.

Different PHP releases, architectures, compilers, distributions and SAPIs can require different offsets and heap-shaping parameters. Apache with mod_php is not interchangeable with PHP-FPM, CLI or an arbitrarily packaged distribution build.

Reliable exploitation is therefore an engineering process, not a single script with a list of version numbers. Builds without a verified profile must remain classified as unverified, not automatically exploitable or non-exploitable.

What administrators should do

Update PHP. Temporary controls reduce exposure but do not replace the fixed releases:

  • PHP 8.5.12

  • PHP 8.4.27

  • PHP 8.3.36

  • PHP 8.2.35

For distribution packages, check the vendor’s package revision rather than relying only on the upstream version string, because security fixes may be backported.

PHP 7.4, 8.0 and 8.1 received source patches without official patched releases. Older branches received no fix.

Check beyond obvious web servers. PHP may also be embedded in appliances, hosting panels or third-party products. Internal-only access is not sufficient protection because exploitation can occur before authentication.

PHP separately disclosed CVE-2026-115560 on October 23. This is a distinct, less severe issue in the same upload-progress code and is not fully addressed by the October 21 releases. Until the follow-up fix is available, keep session.upload_progress.enabled = Off, including on already patched systems.

Detection

Focus on the consequences of exploitation:

  • Successful exploitation: a PHP or web worker such as apache2, php-fpm, php-cgi.exe or w3wp.exe launches

    sh, cmd.exe, or PowerShell. Inspect the shell’s command-line arguments, not only its executable name.

  • Failed attempts: PHP workers crash and restart. Correlate these events with web-server errors and the relevant SAPI logs, including Apache error logs, LiteSpeed worker-restart counters, or PHP-FPM slow logs and emergency restarts.

A worker crash is an investigation signal. It is not, by itself, proof of successful exploitation.

If patching must wait

Apply mitigations in the server’s main configuration and restart the workers. Settings applied through ini_set() or .user.ini are not sufficient.

For CVE-2026-109619, disable:

session.upload_progress.enabled = Off

Normal file uploads continue to work. On PHP 8.5, the advisory also lists fatal_error_backtraces = 0.

For CVE-2026-109618, the advisory describes setting memory_limit = -1 and preventing applications from overriding it. This removes the attacker-controlled out-of-memory condition required by that chain.

At the WAF, blocking only the standard upload-progress field provides incomplete coverage because its name is configurable. Where practical, reject multipart POST requests on routes that do not legitimately accept uploads.

Do not rely solely on post_max_size. Multipart parsing can create memory usage much larger than the request’s transmitted size. Also avoid using RLIMIT_AS or RLIMIT_DATA as a workaround, since resulting mmap() failures can steer execution into the vulnerable path.

Bottom line: install the fixed releases, keep upload progress disabled until the follow-up issue is resolved, and monitor for shells spawned by PHP workers or repeated worker crashes. Cenobe’s current results establish verified RCE for specific builds under documented conditions, not universal coverage across PHP installations.