Magento Malware Removal: StyleSmuggler CVE-2026-75650

unflagdomain Team·UPDATED November 13, 2026

StyleSmuggler (CVE-2026-75650) is a maximum-severity flaw in Magento Open Source and Adobe Commerce that let an unauthenticated visitor run code on a store, exploited in the wild three days before a patch existed. Applying Adobe's hotfix closes that door, and since October a second door in the same template engine, BlockStrap (CVE-2026-103849), needs Adobe's October patch as well. Neither tells you whether anyone walked through first.

TL;DR: StyleSmuggler is CVE-2026-75650: unauthenticated remote code execution in Adobe Commerce and Magento Open Source, rated CVSS 10.0 and found by Sansec, with exploitation confirmed from 2026-09-04 (Sansec, 2026). Adobe shipped hotfix VULN-39341 in advisory APSB26-146 on 2026-09-07, and CISA added the flaw to its Known Exploited Vulnerabilities catalog the next day (CISA, 2026). Every 2.4.4–2.4.9 store is affected, and the attacker leaves a persistent implant disguised as a system process — a patched store is not automatically a clean one. On 2026-10-13 Adobe fixed a second CVSS 10.0 flaw in the same email-template engine, BlockStrap (CVE-2026-103849, bulletin APSB26-153), which the September hotfix does not stop; the two are separate fixes and you need both (Sansec, 2026). Check for compromise, remove it, rotate credentials, then ask each flagging vendor to re-check.

Written for store owners: what the flaw is, whether you were hit before you patched, what cleaning involves, and how to get unflagged afterwards.

What is StyleSmuggler (CVE-2026-75650)?

StyleSmuggler is an unauthenticated remote-code-execution flaw in Magento's template engine, named and disclosed by Sansec on 2026-09-05 after the team found an active campaign the previous day (Sansec, 2026). Adobe rates it CVSS 10.0 — the maximum — and classifies it as CWE-1336, improper neutralization of special elements used in a template engine (Adobe, 2026).

The attack runs in two stages. First, the attacker smuggles PHP source into a file Magento writes for itself — in the observed chain, a failed-payment report under var/report. Then a GraphQL request uses template "styles" properties to make Magento include that file, and the code runs when Magento renders its "Payment Transaction Failed Reminder" email (Sansec, 2026). No login, no user interaction: nobody has to open the email, and a delivery failure still triggers the render.

CISA added the CVE to its Known Exploited Vulnerabilities catalog on 2026-09-08 (CISA, 2026), and this is core code, not an add-on: Sansec reproduced the exploit on clean, unmodified Open Source 2.4.7, 2.4.8 and 2.4.9 stores.

Is my store affected? Versions and the patch

Every Magento Open Source and Adobe Commerce version from 2.4.4 up to and including 2.4.9 is affected (Sansec, 2026). The first known victim was running 2.4.6-p15 with the July and August 2026 patches applied and a clean security:patch-status — fully up to date for the time, because no patch existed yet.

Adobe's fix is the VULN-39341 hotfix, delivered as a composer patch in advisory APSB26-146 on 2026-09-07 (Adobe, 2026). Adobe's tested coverage:

  • Adobe Commerce: 2.4.4 through 2.4.9 (August 2026 builds and earlier).
  • Adobe Commerce B2B: 1.3.3 through 1.5.3.
  • Magento Open Source: 2.4.6 through 2.4.9 as first published, expanded on 2026-09-18 to add 2.4.4 and 2.4.5 (scandiweb, 2026).

Two things to check before you call it done. The hotfix is packaged per patch build — a store on 2.4.8-p2 needs a different package from one on 2.4.8-p1 — so match your exact release. And Adobe's coverage is version-limited: branches 2.2, 2.3 and 2.4.0 through 2.4.3 got no official fix. For those, scandiweb rebuilt the patch for 41 releases from 2.2.0 to 2.4.3-p3 (scandiweb, 2026); Sansec notes it has not reviewed that backport (Sansec, 2026), so weigh it against rebuilding on a supported line.

Since October, the hotfix alone is not enough. Adobe's bulletin APSB26-153 of 2026-10-13 fixed BlockStrap (CVE-2026-103849): another CVSS 10.0 flaw that lets an unauthenticated visitor run code through the same email-template engine, and one the StyleSmuggler hotfix does not cover. The October patch does not contain the StyleSmuggler hotfix either, so keep VULN-39341 installed and add the October 2026 security patch on top. Adobe rated BlockStrap priority 2, with a 30-day target, because no attacks were known; Sansec had seen none on live stores when it published on 2026-10-15 and still advised patching now instead of waiting the 30 days. On Magento Open Source 2.4.4 to 2.4.6, Adobe's October patches require an Adobe Commerce license; Sansec points to a third-party backport it does not vouch for, or a move to 2.4.7-p10 or newer (Sansec, 2026).

The two states are easy to confuse. Unpatched does not mean breached: the flaw still has to be reached on your server, and many stores were never hit. Patched does not mean clean: the hotfix closes the entry point from the moment it is applied, and does nothing about what an attacker who came in earlier left behind.

Was my store already exploited?

Exploitation started on 2026-09-04 and scaled fast: one managed server was hit 50 minutes after the first confirmed attack (reported by Disrex, via eSecurity Planet, 2026). If your store was reachable before you patched, check it rather than assume.

What the attacker leaves:

  • A Rust implant in a system-process costume. Sansec saw it pose as [kworker/u:8:0], then fc-cache, then chronyd, with files under /tmp and ~/.cache/fontconfig/ and cron entries at unusual minutes (Sansec, 2026).
  • A backup channel disguised as NTP traffic on UDP port 123, plus a web shell: a PHP file in the product-image cache under pub/media that 404s unless requested with a specific header (eSecurity Planet, 2026).
  • Poisoned report files. The exploit's first stage writes into var/report; Sansec's check for the observed files is grep -ril 'x_trace_' var/report/ (Sansec, 2026).

Four checks cover most of the ground:

# PHP files that do not belong in the media directory
find -L pub/media -type f -name '*.php'

# report files the exploit's first stage poisoned
grep -ril 'x_trace_' var/report/

# system-process names running under your web user
ps aux | grep -E 'kworker|fc-cache|chronyd' | grep -v grep

# is the October BlockStrap fix really applied? 0 means it is missing
grep -c resolveDeferredDirectives vendor/magento/framework/Filter/Template.php

A kernel-thread name under your web user is the loudest single signal; a clean crontab proves nothing, because one implant variant restarts with no cron entry at all. Diff your code too — one observed variant modified a single core file under vendor/magento/framework/App/View.php — and treat the request log as evidence: later-stage requests carry the string template_styles.

We do not reprint the attacker's hashes and C2 addresses here; the current list is on Sansec's research page.

Patching is not remediation

Adobe's own guidance makes this explicit: after the hotfix, rotate the encryption key and every credential it protects. "Changing the Commerce encryption key does not invalidate secrets an attacker may already have obtained" (eSecurity Planet, 2026).

The rotation list, in Adobe's sequence: maintenance mode, cron off, then the encryption key, admin passwords, integration tokens, OAuth client secrets, payment gateway credentials, database credentials, and SSH or deployment keys; flush caches and restore cron afterwards. Regenerate third-party credentials at the external provider too, not only inside Adobe Commerce — a new dashboard key does not revoke the old one at Stripe, Braintree or Adyen.

One ordering caveat: remove the implant before you rotate, or the attacker simply reads the new secrets. And because the encryption key protects stored configuration, rotation is a controlled procedure — backup, maintenance mode — never a hand edit of app/etc/env.php.

How to clean a hacked Magento store

The cleanup is yours or a specialist's: we do not clean malware, and our service starts only afterwards, with the separate work of asking vendors to re-check the domain.

On Magento, a rebuild is often safer than a surgical clean: tens of thousands of vendored files, generated code, queues and integrations make a planted backdoor very hard to prove absent. Restoring a clean backup taken before 2026-09-04 and re-applying your customizations is a defensible start: then apply both patches before the store goes live again, and remember that orders and customer changes made since that backup are not in it — export them first. Otherwise, clean in place in this order:

  1. Back up first, even a backup you believe is infected.
  2. Apply the hotfix and the October patch, so both doors are closed while you work.
  3. Restore code you can replace: core and vendor/ from your composer.lock; themes and modules from official sources.
  4. Remove the leftovers: PHP files under pub/media, poisoned files in var/report and var/log, and anything the checks above surfaced.
  5. Clear persistence: unknown cron entries in both the system crontab and Magento's own schedule, then unknown admin users and integrations — an attacker's API integration token outlives a password change (Sansec, 2026).
  6. Rotate credentials, in the order set out above.
  7. Re-run the checks from the previous section until they all come back clean.

For a store that earns revenue, professional forensics is worth it — Sansec's eComscan detects and terminates the known StyleSmuggler processes (eSecurity Planet, 2026). Our general walkthrough, how to clean a hacked website, covers the wider sequence.

Why the store can still be flagged after cleanup

While the implant was live, security vendors' crawlers saw what your domain served — a web shell, injected content, a redirect — and recorded it. Those flags can go live on their own schedule, after you have cleaned, and a clean store does not silently clear them: each vendor re-checks separately, on its own cycle, so a flag can outlive the malware.

So once you are genuinely clean, look at your reputation deliberately: our free blocklist check shows which vendors flag your domain, with no signup — a reputation check, not a malware scan. A clean result does not prove a clean store; a flagged result tells you a vendor already saw something and will not reconsider on its own.

If you also run WordPress, the same discipline applies after its own September core flaw; our CVE-2026-87902 walkthrough is that version of this drill.

If vendors still flag the store after cleanup

Once the store is clean and vendors still flag the domain, unflagdomain.com can send the removal requests for a one-time €49 per domain; the pricing page has the rest. A correctly formatted removal request is sent to every flagging vendor that accepts one by email, within 48 hours of payment (in practice within the first hour). Vendors that only take a web form or manual review get a ready-to-paste request on the dashboard.

Preparing for the next one

Adobe ships regular security releases, with out-of-band hotfixes like this one in between, and neither retires the other: the September 2026 release (APSB26-138) does not contain the StyleSmuggler hotfix, and neither does the October patch (APSB26-153). Subscribe to the bulletins, record your exact patch level (including the -p build), and patch through composer so the process is reproducible.

While an emergency patch is pending — or if your line has no fix — virtual patching buys time. Cloudflare added a block rule for CVE-2026-75650 to its managed ruleset on 2026-09-10, and Fastly shipped a virtual patch in its Next-Gen WAF (Cloudflare, 2026; Fastly, 2026). Treat either as cover, not a fix: a WAF rule blocks the known attack shape, and no WAF removes an implant already on the server.

Last, keep the boring things running: file-integrity monitoring, an occasional eComscan-style sweep, off-store backups that predate 2026-09-04, and outbound connections restricted to what the store needs.

Updated is not the same as untouched

If the checks come back clean and both patches are applied, you can stop there. If they come back dirty, finding out now costs a cleanup; later it can cost a cleanup plus a domain that vendors have already flagged. Either way, start by knowing where you stand: check your domain across the security vendors, free and without an account.

// FAQ
  • It is a critical remote-code flaw in Magento Open Source and Adobe Commerce, rated CVSS 10.0, found by Sansec and exploited from 2026-09-04. Adobe published the APSB26-146 hotfix on 2026-09-07; the flaw let an unauthenticated attacker run code on an unpatched store.

  • Adobe's advisory covers Adobe Commerce and Magento Open Source 2.4.4 through 2.4.9, with the B2B extension in its own version range. Check APSB26-146 for the exact list before acting, because Adobe expanded coverage after the emergency release.

  • Not from the hotfix alone. It closes StyleSmuggler's entry point, but on 2026-10-13 Adobe fixed a second CVSS 10.0 flaw in the same email-template engine, BlockStrap (CVE-2026-103849, APSB26-153), which the hotfix does not stop; Sansec says you need both fixes. And patching is not remediation: if the store was already exploited, the attacker's code can persist after the update. Adobe's guidance includes rotating encryption keys and credentials, and you should check the published indicators for signs of an implant.

  • Magento cleanups are more involved than WordPress ones and a rebuild from clean code is often safer than a surgical removal, so most owners work with a developer. We do not clean malware — our service is the separate step of requesting re-checks from the vendors flagging the domain.

  • Security vendors re-check a domain on their own cycle or when they receive a request, so flags can outlive the malware. Each vendor is requested separately, and each decides the outcome on its own schedule.