
StyleSmuggler fix: patch the Magento and Adobe Commerce RCE
Aikido Security's writeup on "StyleSmuggler," a remote code execution vulnerability in Magento and Adobe Commerce, covering the fix/patch for the flaw. Page content was not retrieved, so specifics of the exploitation technique and affected versions could not be confirmed directly.
What it is
StyleSmuggler is an unauthenticated remote code execution zero-day affecting every current version of Magento Open Source and Adobe Commerce, including 2.4.9. Sansec published research on September 5, 2026; exploitation has been active since September 4. Adobe has since released urgent hotfixes and the flaw is now tracked as CVE-2026-75650 (CVSS 10.0). Aikido tracks it as AIKIDO-2026-248927 (Magento Open Source), AIKIDO-2026-123768 (Adobe Commerce), and AIKIDO-2026-724507 (Magento Cloud metapackage).
How it works
The exploit is a two-stage deferred-execution chain, both stages abusing existing Magento functionality:
flowchart TD
A[Unauthenticated GraphQL request] -->|PHP injected via style properties| B[Payload written to a Magento-generated file<br/>e.g. checkout failure report]
B -->|no immediate execution| C[Payment Transaction Failed Reminder email rendered]
C -->|server-side template rendering| D[PHP executes — RCE]
D --> E[Rust backdoor disguised as kernel thread]The payload is smuggled through CSS style properties on a GraphQL request, written into a file Magento generates itself (such as a checkout failure report), then executed later when Magento renders a Payment Transaction Failed Reminder email. Crucially, the email does not need to be delivered — code runs server-side during template rendering. Confirmed intrusions installed a persistent Rust-based backdoor disguised as a kernel thread, surviving reboot and sometimes lying dormant for hours before activating.
Preconditions / Affected
Every current version is vulnerable; Sansec reproduced the full chain on clean 2.4.7, 2.4.8, and 2.4.9 installs. One confirmed victim ran 2.4.6-p15 with July and August 2026 security patches fully applied — patch status did not help. No credentials, session, or user interaction required. GraphQL is the entry point the exploit depends on.
What to do
- Check exposure against your Aikido Intel entry (AIKIDO-2026-248927, -123768, or -724507); each documents the injection point and trigger condition.
- Apply the Aikido Libraries drop-in fix for your branch. Released branches:
2.3.1-p12007002+aikido2.4.7-p1012007002+aikido2.4.8-p512007002+aikido- If you cannot patch immediately, disable GraphQL as an interim mitigation.
- Rotate Magento credentials if you find any evidence of compromise, since the backdoor has been observed sitting dormant before activating.
The Aikido patch sanitizes template styles before Magento's engine processes them, applied at two points depending on version; legitimate CSS passes through untouched.
Caveats
Disabling GraphQL takes any headless or PWA storefront offline and only hardens against the current attack pattern — the underlying flaw stays open until a real fix ships. Aikido's fix is a third-party drop-in replacement, not an official Adobe release. The page notes Adobe's next scheduled security release was September 8 but was not confirmed to cover StyleSmuggler; note the page also carries an update stating Adobe later shipped urgent hotfixes under CVE-2026-75650.
CVEs named here
Technologies named here
- Aikido Libraries
- Magento Open Source
- Adobe Commerce
- Aikido Intel
- Magento 2.4.6-p15
- Magento Cloud metapackage
- Magento
Techniques named here
- PHP injection via style properties in GraphQL request
- Delayed execution via generated file
- Template rendering RCE via email generation
- Persistent backdoor disguised as kernel thread
- Magecart-style skimmer injection
Threat actors named here
- Stylesmuggler
- Rust-based backdoor
Related in AppSec
Flowise MCP Security Bypass Enables RCE
Inside an Oracle Database SQL Injection Attack | Huntress
OASIS
