On this page · 5 sections
TL;DR
- PHP2Shell is the exploit tool that chains two memory-safety flaws in the PHP engine, CVE-2026-109618 and CVE-2026-109619, rated CVSS 9.2 (v4.0). Clean Adobe Commerce (Magento 2) code doesn't protect you.
- Fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released 21 October 2026. PHP 8.1 and older get no php.net release.
- Upgrade PHP first. The temporary mitigations are a bridge with real costs, and one of them, upload progress off, stays on after the upgrade because of a third CVE, CVE-2026-115560, disclosed two days later. As of 10 November 2026 its fix had not shipped.
Your code review can't catch this one. The vulnerable code sits in the PHP runtime, it has been there since PHP 5.4 (Sansec), and it's reachable without logging in. On 21 October 2026 the PHP project shipped fixes for two flaws. PHP2Shell is the name of the exploit tool that chains them. Adobe Commerce, WordPress, Shopware and WooCommerce are all in scope, because they all run on the same engine.
I heard about it a few days after the release. Most hosts were done quickly. The PHP 8.1 ones took longest, because php.net ships no fix for them and each one needed its own plan.
The two flaws: CVE-2026-109618 and CVE-2026-109619
CVE-2026-109618 is memory corruption triggered when PHP runs out of memory at exactly the wrong moment; according to Sansec, the same path can also leak memory from other requests. CVE-2026-109619 is a use-after-free caused by global state left behind after a fatal error. A CVSS score of 10.0 circulated when the CVE IDs leaked the day before release. The real score is 9.2, which is still critical.
The sources disagree, so read more than one
- The PHP Foundation says full code execution was demonstrated with default settings on
mod_php, and that no working exploits were known at release. - Sansec, which monitors Magento and Adobe Commerce stores closely, cites a researcher who found the public proof-of-concept code didn't work against a default install, and says real attacks need knowledge of the target plus specific server conditions. It also relays Cloudflare's report of attacks more than six hours before the release.
Those positions aren't contradictory so much as different threat models. Mine: if exploitation was observed before the fix, I assume my stack is exploitable until I've proven otherwise. Waiting for a reliable public exploit before patching is an anti-pattern.
The order I'd work in
- Inventory every PHP binary. Run
php -von every web node, worker and cron host, not just the one you usually SSH into. Container base images count too. - Upgrade to the fixed release on your supported line. Adobe's system requirements list PHP 8.5 for 2.4.9, 8.4 or 8.3 for 2.4.8, and 8.3 or 8.2 for 2.4.7, so that's 8.5.12, 8.4.27, 8.3.36 or 8.2.35. The Composer constraint of 2.4.9 also accepts 8.4 and 8.3, but Adobe doesn't list them as supported. Don't jump a minor version your Commerce release doesn't support. If the fixed release is a minor version up from where you are, PHPCompatibility lists the files and lines to check first.
- On PHP 8.1 or older, there's no php.net release. The PHP security team published source patches for 7.4, 8.0 and 8.1, and several distributions and LTS vendors backported them, keeping the same version number. Ask your provider which build you're on, in writing, and schedule the real upgrade this sprint.
- Bridge only if you can't upgrade today. The published mitigations are blocking
multipart/form-dataat the web server, settingsession.upload_progress.enabled=0, and settingmemory_limit=-1, which only helps if nothing in the application sets it back. On Adobe Commerce something does:pub/.user.inisetsmemory_limit = 756M, and under PHP-FPM that wins overphp.ini. Set it in the FPM pool withphp_admin_value[memory_limit] = -1instead, which.user.inican't override. That last one is in the official guidance, and it has a real cost: one request can now use all the server's memory. CERT-EU pairs it with a container or cgroup memory limit, so a runaway request kills one worker instead of the server. Don't use it without that limit. - Keep
session.upload_progress.enabled=0after the upgrade. On 23 October PHP disclosed a third flaw, CVE-2026-115560, which it considers an unlikely risk, and said it would be fixed in the next regular release rather than out of band. Until that release ships, its advice is to keep upload progress off. As of 10 November 2026 the latest php.net releases were still 8.5.12, 8.4.27, 8.3.36 and 8.2.35, so the fix for CVE-2026-115560 had not shipped. - Verify the running process, not the package. Re-run
php -v, and confirm PHP-FPM restarted. A patched binary on disk does nothing while the old pool keeps serving requests. The quick note on checking whether your PHP has the PHP2Shell fix has the commands, including the one for the FPM binary.
| PHP branch | Fixed release (21 October 2026) |
|---|---|
| 8.5 | 8.5.12 |
| 8.4 | 8.4.27 |
| 8.3 | 8.3.36 |
| 8.2 | 8.2.35 |
| 8.1, 8.0, 7.4 | No php.net release; source patches from the PHP security team |
Why blocking uploads is awkward on Adobe Commerce
Adobe Commerce needs file uploads in the admin, and often on the storefront: product images, import files, customer attachments. Blocking multipart requests site-wide breaks real features, and Sansec notes that some stores submit cart or checkout forms as multipart too. If you must use the multipart block, scope it to paths that never take uploads, place a test order after adding it, and remove it the day the upgrade ships.
What separated fast teams from slow ones
Engine-level bugs are rare, but the teams that patched within a day shared a few habits: they knew which PHP version ran on which host, their PHP upgrades went through the same pipeline as application code, and automated checks told them within minutes whether the store still worked. If any of those were missing for you this time, that's the work to schedule once the patch is out. The Commerce patches from the same weeks have their own runbook.
Sources
The PHP Foundation release notes, the php.net security advisory of 21 October, Sansec's analysis and the CERT-EU advisory.


