Key facts
| Fact | Detail |
|---|---|
| Product | Adobe Commerce, Commerce B2B and Magento Open Source (e-commerce platform) |
| Affected versions | Commerce and Open Source 2.4.9-2026-aug and earlier; B2B 1.5.3-2026-aug and earlier |
| Fixed in | VULN-39341 hotfix (APSB26-146) plus the 2026-oct releases (APSB26-153) |
| Severity | 10.0 Critical (CVSS 3.1, Adobe) |
| Who can attack | Anyone on the internet; no login and no user action needed |
| Exploited | Yes: in CISA's KEV catalog since 8 September 2026; Sansec saw the first attack on 4 September 2026 |
| CVE published | 7 September 2026 |
What an attacker can do
CVE-2026-75650 is a template injection flaw. An attacker sneaks a command into the template engine Magento uses to build store emails. The command makes Magento load and run PHP code the attacker planted on the server earlier. The result is remote code execution (the attacker runs their own code on your server), with no account needed. Sansec, which found it, calls it StyleSmuggler.
The attacker first plants PHP code, for example through the /paypal/transparent/response/ address. Magento then runs it through a failed-payment email or a request to /graphql.
On hacked stores, Sansec found a backdoor and a PHP web shell (a file that takes commands from a browser). It also found code in a core Magento file that fetches more attacker code, and a card skimmer (code that copies card details typed at checkout) in the database. Adobe says to replace the encryption key and every secret it protected, payment gateway credentials included.
Who is affected
Adobe's bulletin APSB26-146 lists these versions, on all platforms:
- Adobe Commerce 2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug, 2.4.5-2026-aug, 2.4.4-2026-aug and earlier
- Adobe Commerce B2B 1.5.3-2026-aug, 1.5.2-2026-aug, 1.4.2-2026-aug, 1.3.4-2026-aug, 1.3.3-2026-aug and earlier
- Magento Open Source 2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug and earlier
Sansec says every version from 2.4.4 to 2.4.9 is affected. A recent security release does not protect you if the VULN-39341 hotfix is missing. Changing where the store keeps login sessions (Redis or the database) will not stop the attack either. Adobe publishes no fix for 2.4.3 and older, so those stores need an upgrade.
How to check your version
From the Magento root folder, run:
bin/magento --version
In the Magento Admin, the version shows at the bottom right of the page. With Composer, run the line for your edition (Magento Open Source first, then Adobe Commerce):
composer show magento/product-community-edition
composer show magento/product-enterprise-edition
You can also search the composer.lock file for these two package names.
On Adobe Commerce on Cloud, Adobe gives a command to check the hotfix. Install Adobe's Quality Patches Tool first, then run:
vendor/bin/magento-patches -n status | grep "39341\|Status"
The hotfix line should show the status "Applied".
What to do now
Apply Adobe's hotfix today. Download the VULN-39341 zip for your version from Adobe's APSB26-146 knowledge base article, then unzip it. If you host the store yourself or run Magento Open Source, upload the .patch file to the Magento root folder. Its name looks like VULN-39341_Hotfix_COMPOSER.patch. Then run:
patch -p1 < <patch file>
If that fails, run it with -p2 instead:
patch -p2 < <patch file>
Then refresh the cache in Admin > System > Tools > Cache Management, or run:
bin/magento cache:flush
On Adobe Commerce on Cloud, copy the file into your project's m2-hotfixes folder, then commit and push it.
Install the October 2026 update (APSB26-153) as well, since Adobe says you need both. It fixes CVE-2026-103849, a second flaw that Sansec says gets around the hotfix. This update covers Adobe Commerce 2.4.4 to 2.4.9 (2.4.x-2026-oct) and B2B 1.3.3 to 1.5.3. For Magento Open Source it covers only 2.4.7 to 2.4.9, so older stores must upgrade to one of these releases.
Next, replace the encryption key and every secret it protected, following the 15-step procedure in the same APSB26-146 article. A new key alone does not cancel credentials already exposed.
Patching does not clean a store that was already hit. Among the signs Sansec lists:
- processes named
[kworker/u:8:0],fc-cacheorchronyd - changes to
vendor/magento/framework/App/View.php - base64 code in
core_config_data, atdesign/head/includes - traffic to
99.84.67.186 - PHP files under
pub/media(the command below lists them) - UDP port 123 traffic to
185.157.160.251orntp.timesync.to(the fc-cache and chronyd builds)
Normal system programs also use the last two process names, so check where each process runs from. To list PHP files under pub/media, run this from the Magento root folder:
find -L pub/media -type f -name '*.php'
Sansec's write-up, in the sources below, gives the full list of signs to check.
Is it being exploited?
Yes. Sansec saw failed attack attempts on 23 August 2026 and the first confirmed attack on 4 September 2026 at 22:20. It gives no count of affected stores. The first attack came before any fix existed, since Adobe released the hotfix on 7 September 2026. On the day of the fix, Sansec also caught a second, unrelated attacker installing a PHP web shell.
Adobe's bulletin says: "Adobe is aware of CVE-2026-75650 being exploited in the wild." CISA (the US government's cyber defence agency) added the flaw to its Known Exploited Vulnerabilities catalog on 8 September 2026. It lists ransomware use as unknown. It also rates the attack as automatable, so one script can try it against many stores.
Get help
Updating closes this flaw. Flaws in your own code get no CVE and no update, and a test of your app is how they are found.
A penetration test of your web app and its API: who can see whose data, and what an attacker can change.
From AED 20,000, excl. 5% VAT
Sources
- CVE-2026-75650 record CVE Program
- Security update available for Adobe Commerce | APSB26-146 Adobe
- Urgent Action Required: Critical Security Update Available for Adobe Commerce (APSB26-146) Adobe Experience League
- Security update available for Adobe Commerce | APSB26-153 Adobe
- StyleSmuggler: Magento and Adobe Commerce 0-day RCE (CVE-2026-75650) under active attack Sansec
- Known Exploited Vulnerabilities Catalog CISA