SECURITY Signal 56
Unauthenticated RCE StyleSmuggler hits all current Magento and Adobe Commerce versions with no Adobe patch yet
A zero-day named StyleSmuggler gives unauthenticated attackers remote code execution against every current version of Magento Open Source and Adobe Commerce, has been under active exploitation since September 4, and Adobe has not yet released a CVE or patch.
Every current Magento and Adobe Commerce deployment is vulnerable, including fully patched installs, and the only vendor mitigation, disabling GraphQL, takes headless storefronts offline. Aikido has shipped drop-in replacement packages that sanitize template styles without requiring a platform version upgrade, but teams not using Aikido have no official fix to apply.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The exploit injects PHP through GraphQL style properties and executes it server-side during template rendering of a Payment Transaction Failed Reminder email, requiring no authentication and no email delivery.
Confirmed intrusions have installed a persistent Rust-based backdoor disguised as a kernel thread that survives reboots, exposing customer PII, payment details, and admin credentials.
Aikido has released patched packages for branches 2.3.1, 2.4.7, and 2.4.8 that sanitize template styles before Magento's engine processes them, while Adobe's next scheduled security release is September 8 with no confirmed coverage.
THE READ
What the cluster adds up to.
StyleSmuggler is an unauthenticated remote code execution vulnerability affecting every current version of Magento Open Source and Adobe Commerce, including 2.4.9. Sansec published research on September 5 after active exploitation began September 4. One confirmed victim was running 2.4.6-p15 with the July and August 2026 security patches fully applied, meaning current patch status does not prevent the attack. Adobe has not published an advisory, assigned a CVE, or released a patch, and its most recent Commerce security bulletin dates to August 11.
The exploit runs in two stages using existing Magento functionality. An unauthenticated attacker injects PHP through style properties on a GraphQL request, which does not execute immediately but gets written into a file Magento generates itself, such as a checkout failure report. The payload executes later when Magento renders a Payment Transaction Failed Reminder email template, running server-side during rendering regardless of whether the email is delivered. Confirmed intrusions installed a persistent Rust-based backdoor disguised as a kernel thread that survives reboots and can sit dormant before acting.
Aikido has shipped drop-in replacement packages that fix the vulnerability without requiring a Magento or Adobe Commerce version upgrade. The patches sanitize template styles before Magento's engine processes them, closing the path StyleSmuggler uses to reach directive and dependency-injection processing. Patches are available for branches 2.3.1-p12007002+aikido, 2.4.7-p1012007002+aikido, and 2.4.8-p512007002+aikido, and can be pushed in bulk across multiple sites. Legitimate CSS passes through untouched, and the fix is applied at two points depending on the version to match the two ways the vulnerable code handles style data.
For teams not using Aikido, the only interim mitigation is disabling GraphQL, which is the entry point the exploit depends on. This is a significant trade-off for headless or PWA storefronts that go offline the moment GraphQL is blocked, and it only hardens against the current attack pattern without closing the underlying flaw. Adobe's next scheduled security release is September 8, but whether it covers StyleSmuggler is unknown.
Aikido Intel has rated the vulnerability critical across three affected packages: AIKIDO-2026-248927 for Magento Open Source, AIKIDO-2026-123768 for Adobe Commerce, and AIKIDO-2026-724507 for the Magento Cloud metapackage. Each entry documents the injection point and trigger condition, allowing teams to confirm exposure without waiting for Adobe. The exposure from successful exploitation includes customer PII, payment transaction details, admin credentials, database contents, and Magecart-style skimmer injection against shoppers.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER
↗