1. Red
  2. Learn
  3. Ecommerce

PHP2Shell and Magento / Adobe Commerce: verify the runtime

Magento and Adobe Commerce run on PHP, so PHP2Shell applies. Which PHP each 2.4.x release supports, which fixed build to target, and how to verify the workers.

By Timothy Lindblom, FounderPublished 4 November 20268 min readHow we check facts
On this page
  1. Does PHP2Shell affect Magento and Adobe Commerce?
  2. Which PHP can my Magento release run?
  3. What is the trap with Magento specifically?
  4. How do I fix it?
  5. Does a WAF or Sansec Shield cover it?
  6. Am I affected? A three-state self-test
  7. Was my store exploited before I patched?
  8. What can the free scan tell me?

Magento Open Source and Adobe Commerce run on PHP, so PHP2Shell (CVE-2026-109618 and CVE-2026-109619) applies to every store, and no Magento patch fixes it. The fix is a patched PHP on each server that serves the store, then restarted workers. Which PHP you may move to depends on your 2.4.x release, so read Adobe's compatibility table first.

FactDetailSource
CVE idsCVE-2026-109618 and CVE-2026-109619, both CVSS v4 9.2PHP notice
Fixed upstream builds8.5.12, 8.4.27, 8.3.36, 8.2.35PHP notice, changelog
Older branches8.1 and older get no PHP project release. Source backports exist for 7.4, 8.0 and 8.1PHP notice
Magento namedSansec lists Magento 2.4.9 among affected platforms (vendor research, updated 22 October 2026)Sansec
ExploitationHoneypot attempts from 17 October (AWS, vendor-claimed). No confirmed named victim in a primary source at our checkAWS
CISA KEVBoth CVEs added 26 October 2026, federal due date 29 OctoberCISA KEV
Checked4 November 2026this page
9.2CVSS v4 score, both CVEs
4PHP branches with a fixed upstream build
31 Dec2026, last security support for PHP 8.2

Does PHP2Shell affect Magento and Adobe Commerce?

Yes, because Magento is a PHP application. The PHP project says every installation that serves web requests is in scope: PHP-FPM, mod_php, CGI, FrankenPHP and LiteSpeed. Sansec puts it directly: the flaws sit in the PHP engine, so Magento stores are affected even when their own code is in good order.

The two bugs are memory-safety problems that an unauthenticated web request can reach. We do not describe how, and you do not need it to fix a store. The UK NCSC asks organisations to inventory their PHP systems, update, and take a system offline if neither an update nor a mitigation is possible.

If your store is on Shopify, or any platform with no PHP, this bug is not yours. Magento and Adobe Commerce always are PHP. More store guides are in the other ecommerce articles.

Which PHP can my Magento release run?

This is the question the generic PHP2Shell advice skips. A Magento release supports only certain PHP branches, and some of those branches have no fixed upstream build.

Magento releasePHP Adobe listsFixed upstream buildWhat it means
2.4.98.58.5.12Update to 8.5.12 or later
2.4.8 (p4, p5)8.4, 8.38.4.27, 8.3.36Update within your branch
2.4.7 (p9, p10)8.3, 8.28.3.36, 8.2.35Prefer 8.3. 8.2 security support ends 31 December 2026
2.4.6 (p14, p15)8.2, 8.18.2.358.2 has a fix. 8.1 needs a vendor backport
2.4.5 (p16, p17)8.1none upstreamVendor backport, or upgrade Magento
2.4.4 (p17, p18)8.1none upstreamVendor backport, or upgrade Magento

PHP columns from Adobe's system requirements, last updated 13 October 2026, checked 4 November. Fixed builds and the 8.2 date from the PHP notice and supported versions.

Two readings of that table matter. A store on 2.4.4 or 2.4.5 has only PHP 8.1 on Adobe's list, and 8.1 is the branch with no release. A store on 2.4.6 is on a release whose regular support ended on 11 August 2026 per Adobe's lifecycle page (updated 14 October 2026), with extended support to 31 August 2027.

Adobe's 2.4.9 notes, as the page we read presents them, list 8.5 only. We did not confirm whether a given 2.4.9 patch level accepts 8.4. Read the row for your exact patch level before you move. How long each release stays supported is covered in the Magento support lifecycle guide.

What is the trap with Magento specifically?

Magento stores rarely run one PHP. A typical setup has web nodes, a cron container, queue consumers started from the command line, a staging copy and a build image. Each can carry its own PHP, and a patch on the web tier says nothing about the rest.

Three confusions come up:

  1. The admin shows the Magento version, not the PHP build. A store on 2.4.7-p10 can sit on any PHP in its range, fixed or not.
  2. Moving to a fixed PHP outside Adobe's list is unsupported. A 2.4.5 store cannot just install 8.4. Its routes are a backport on 8.1, or a Magento upgrade.
  3. The Magento security patch you already applied does not count. The September StyleSmuggler hotfix and the PHP fix sit in different layers, as the next table shows.
TaskLayerWho ships itDone when
StyleSmuggler, CVE-2026-75650Magento application, a Composer patchAdobe, APSB26-146, 7 September 2026Patch status listed on the server. See our StyleSmuggler page
PHP2Shell, CVE-2026-109618 and CVE-2026-109619PHP engine, the runtimePHP project, your OS or hosting vendorA fixed package is installed and the workers started after it

A store can have done the first and not the second. Both belong on the same Magento security checklist.

Five steps from Adobe's PHP table to evidence you can show 1. Adobe's table PHP for your release 2. Fixed PHP or vendor backport 3. Package in changelog names CVEs 4. Workers restarted web, cron, consumers 5. Evidence kept build + start time A step done on the web tier alone leaves cron and consumers on the old build.
Verifying a Magento runtime: the job is finished at step 5, not step 2.

How do I fix it?

If a host, an agency or Adobe Commerce Cloud runs the PHP

We found no Adobe statement on PHP2Shell at our check on 4 November 2026, so the answer has to come from Adobe support. Ask, and keep the reply:

For [your store], which PHP build serves the storefront, admin, cron and queue consumers in every environment (production, staging, and any build image)? Does that build's changelog name CVE-2026-109618 and CVE-2026-109619? When were the PHP workers last restarted or replaced, and do I need to redeploy or change a setting?

  • Get the PHP build identifier per environment, in writing
  • Get the worker restart or redeploy time
  • Ask whether your Magento release supports the PHP they installed (compare with the table above)
  • Ask for the same answers for the staging copy and any build image

If you run the servers yourself

  • Find your release's row in the table and choose the newest PHP on it that has a fixed build
  • Update PHP through your distribution or vendor, then read the changelog for both CVE ids. Ubuntu published a fixed 8.1 package for 22.04. Our Ubuntu and Debian page covers backport version strings
  • Test on staging first: checkout, admin, an import, cron and a queue consumer
  • Restart PHP-FPM or Apache, then restart cron and queue consumers so none runs on the old binary. Checking the restart took effect has its own page
  • Rebuild and redeploy any container image that bundles PHP
  • Confirm the web PHP, not the CLI. php -v reports the command line binary only

Step by step commands per distribution are on the fix page.

What if I cannot move this week?

The PHP notice lists interim settings and calls updating the only complete solution. For CVE-2026-109618 it suggests memory_limit=-1 set at server level, a low post_max_size (8M with no uploads, 32M with), and request limits at the frontend. For CVE-2026-109619 it suggests session.upload_progress.enabled=0, set in php.ini or the pool rather than at runtime. On 23 October PHP recommended that same setting for a third issue, CVE-2026-115560.

Check any limit against your admin image uploads and product imports before lowering it, then restart every worker. If you are on 2.4.4 or 2.4.5, also read our PHP 8.1 and older page. The PHP project published an 8.1 source backport, which is a source branch and not a release. Treat it as a stopgap for someone who can build and test PHP.

Does a WAF or Sansec Shield cover it?

Not in place of the patch. Cloudflare says it deployed WAF rules to free and paid plans from 03:02 UTC on 21 October (vendor-claimed) and still tells customers to patch. Traffic that reaches your origin by another route does not pass through that edge.

Sansec is direct about its own product. Its research page says the paths run inside PHP, before store code and before Shield, and tells stores not to wait for a Shield rule. Its page also says wide-scale attacks looked less likely than it expected, because they need specific knowledge of the target server. That is a vendor judgement from 22 October, and it is no reason to wait.

Am I affected? A three-state self-test

Am I affected? Where you stand right now

A check from outside can read headers and version hints. It cannot see your package changelog, which PHP serves each Magento tier, or when workers last started.

  1. Detected Your store serves PHP and the version it shows is below the fixed build for its branch. Treat it as exposed. Update to a build on Adobe's list for your release and restart, or send your host the question above today.
  2. Unknown The version is hidden, could be a backport, or you cannot tell which PHP serves the admin, cron and consumers. This is the common case. Get the build identifier and the restart time from the server, your agency or Adobe support.
  3. Confirmed by owner evidence You hold a changelog naming both CVEs, and a service start time after the install, for every tier. The runtime is patched. Whether anything got in before then is a separate question.

No scan, ours included, moves you from "unknown" to "confirmed".

Was my store exploited before I patched?

Attempts began before disclosure. AWS recorded a honeypot attempt on 17 October, four days before the advisory, and says it is unclear whether such attempts would work on real systems. CISA added both CVEs to its Known Exploited Vulnerabilities catalog on 26 October, its list of flaws with reliable evidence of attacks in the wild. At our check on 4 November no primary source we read had published a confirmed, named compromise of a Magento store.

That leaves the look-back to you. If your PHP was unpatched and reachable from 17 October, review web and PHP logs from that date for unusual multipart requests. Look for unexpected PHP files in media and var directories, cron entries and admin users you did not create, and outbound connections from the web server. If checkout pages may have been altered, finding a checkout skimmer is a separate job.

Patching does not remove what was planted earlier. If you find signs of entry, rebuild from a known good source and rotate credentials at each provider, following the step-by-step secret rotation order. Our page on was my site exploited lists the indicators in more detail. For the other store incidents in October, see the ecommerce roundup.

What can the free scan tell me?

The free scan identifies the technologies your site serves and matches each version to known vulnerabilities. It is a lookup: it can say a version is affected, not whether your setup is exposed. It cannot see a vendor backport, which PHP serves your cron tier, or whether workers restarted. The full scan is $100 per scan and sends an AI red team at what is reachable from outside. For the wider picture, read the background on the PHP2Shell flaw.

Questions people ask

Does updating Magento or Adobe Commerce fix PHP2Shell?

No. The bugs are in the PHP engine under Magento, so a Magento patch level or extension update does not change them. The fix is a patched PHP on every server that serves the store, followed by a restart of the PHP workers. Keep applying Adobe's security patches as well, because they cover different bugs.

Which PHP version should I move my Magento store to?

The newest PHP that Adobe lists for your exact release, at or above the fixed build for that branch. Adobe lists 8.5 for 2.4.9, 8.4 and 8.3 for 2.4.8, 8.3 and 8.2 for 2.4.7, 8.2 and 8.1 for 2.4.6, and 8.1 for 2.4.5 and 2.4.4 at our 4 November check. Moving outside that list is unsupported by Adobe.

My store is on 2.4.5 and PHP 8.1. What are my options?

The PHP project shipped no 8.1 release, only a source backport. Ask your OS or hosting vendor for an 8.1 package whose changelog names CVE-2026-109618 and CVE-2026-109619, as Ubuntu 22.04 has. The longer route is a Magento upgrade to a release that supports a branch with a fixed build.

I am on Adobe Commerce Cloud. Who patches the PHP?

We found no Adobe statement on PHP2Shell at our 4 November check. Ask Adobe support which PHP build runs your environments, when it changed, and whether you must redeploy. Keep the written answer.

Does a WAF or Sansec Shield protect my Magento store?

It reduces some exposure and does not replace the patch. Sansec says the flaws run inside PHP, before store code and before Shield, and tells stores to update PHP. Cloudflare says its WAF rules are a stopgap and still recommends patching.

How do I know my store was not hit before I patched?

From outside, you cannot know. Review web and PHP logs from 17 October for unusual multipart requests, then look for new PHP files, cron entries, admin users and outbound connections from the web server. Patching does not remove anything planted earlier.

Sources

  1. PHP security notice, 21 October 2026, with the 23 October follow-up (php.net)CVE ids, fixed releases, scope, end-of-life statement, source backports for 7.4, 8.0 and 8.1, interim settings. Checked 4 November 2026.
  2. GHSA-w8hw-w9fx-j79w: CVE-2026-109618 (php/php-src advisory)
  3. GHSA-6wmf-4rv5-p3rp: CVE-2026-109619 (php/php-src advisory)
  4. PHP 8 changelog (php.net)8.5.12 and 8.4.27 entries dated 22 October. No later release listed at our 4 November check.
  5. PHP supported versions (php.net)Security support end dates per branch. 8.2 ends 31 December 2026. Checked 4 November 2026.
  6. Adobe Commerce system requirements: PHP support by release (Experience League)Page shows last updated 13 October 2026, unchanged at our 4 November check. Source of the version table on this page.
  7. Adobe Commerce software lifecycle: release versions (Experience League)Page shows last updated 14 October 2026. Support end dates for 2.4.4 to 2.4.9.
  8. Sansec: PHP2Shell research (updated 22 October 2026)Lists Magento 2.4.9 among affected platforms and says its Shield cannot stand in for a PHP update. Vendor research.
  9. Amazon Threat Intelligence: PHP2Shell exploitation attempts seen in MadPot honeypots before disclosure (AWS Security Blog)Vendor telemetry. First attempt on 17 October; AWS says it is unclear whether attempts would succeed on real systems.
  10. Cloudflare: WAF protections for the PHP vulnerabilitiesVendor-claimed WAF rollout from 03:02 UTC on 21 October. Cloudflare still tells customers to patch.
  11. UK NCSC: critical security issue affecting PHP (21 October 2026)
  12. CISA Known Exploited Vulnerabilities catalog (CSV feed)Both PHP2Shell CVEs added 26 October 2026, federal due date 29 October. Checked 4 November 2026.
  13. Canonical: PHP2Shell vulnerability fixes available (Ubuntu blog)Includes a fixed PHP 8.1 package for Ubuntu 22.04.
  14. Adobe security bulletin APSB26-146 (StyleSmuggler, 7 September 2026)A separate Magento bug fixed at the application layer. Used here only to separate the two fixes.

Facts on this page are dated and point at the primary source next to them. If a vendor status changes after the date shown, the vendor's page wins; tell us at support@run.cloud and we will update it.