Back to Blog Homepage
    Deploy Blog
    Nathan Chick

    StyleSmuggler (CVE-2026-75650): the Magento Zero-Day That Was Exploited Before the Patch

    A CVSS 10.0 unauthenticated RCE in Magento and Adobe Commerce was actively exploited for three days before Adobe's emergency hotfix landed. Here's what StyleSmuggler is, who it hit, and what to check right now.

    StyleSmuggler (CVE-2026-75650): the Magento Zero-Day That Was Exploited Before the Patch

    This is the one we'd hoped not to have to write this year. StyleSmuggler, tracked as CVE-2026-75650, is a maximum-severity (CVSS 10.0) unauthenticated remote code execution vulnerability in Magento Open Source and Adobe Commerce, and it was a genuine zero-day: attackers were using it before anyone outside the attack had a chance to patch. Sansec's research and Adobe's emergency bulletin are both worth reading in full if you manage a store directly. This post covers what you need to know and do today.

    Risk Overview

    • No authentication is required. The vulnerable endpoints are reachable by anyone who can send a request to your storefront.
    • The attack runs in two stages. First, malicious PHP is injected via a template's styles properties parameter, slipping past Magento's existing safeguards. Second, that code executes later, when Magento processes a failed-payment email or otherwise evaluates the templated content it just stored. The main entry points observed are /paypal/transparent/response/ and /graphql.
    • Sansec confirmed active exploitation from 22:20 UTC on 4 September 2026, three full days before Adobe's hotfix. Multiple stores were compromised in that window, including some already running the August patches, which is exactly what makes this a true zero-day rather than an "unpatched but known" issue.

    Timeline

    Date (2026) Event
    4 September, 22:20 UTC First confirmed exploitation in the wild
    5 September Public disclosure; Sansec Shield begins live blocking
    7 September, 20:20 UTC Adobe ships emergency hotfix, APSB26-146
    10 September Cloudflare and Imperva ship their own WAF rules
    14 September Sansec's research updated with final indicator-of-compromise detail

    Affected Versions

    • Magento Open Source and Adobe Commerce 2.4.4 through 2.4.9 (essentially every currently supported release).
    • Versions 2.2, 2.3 and 2.4.0–2.4.3 are past official support and have no Adobe patch, though community backports exist.
    • If you're on Adobe Commerce Cloud, Adobe applied a virtual patch via Fastly (described in their notes as "accord-rce" VCL rules) that blocks the template-directive save at the edge, which bought cloud customers some protection even before the hotfix landed, but it is not a substitute for applying the actual fix.

    How to check whether you were already hit

    Even if you've now patched, this was exploited for three days before a fix existed, so a compromise check isn't optional. Sansec's indicators of compromise include:

    • Suspicious running processes disguised as system tasks: [kworker/u:8:0], fc-cache, chronyd
    • Implant files at ~/.cache/fontconfig/fc-cache and /tmp/.chrony-<8hex>/chronyd
    • Outbound connections to ntp.timesync.to and 99.84.67.186:443
    • Web shells planted at paths like pub/media/catalog/product/cache/ss_<10hex>/sync_<10hex>.php

    If you find any of these, treat it as a full compromise: rotate all keys and credentials, and don't assume removing the file is sufficient.

    Recommended Actions

    1. Apply APSB26-146 immediately if you haven't already. This is separate from the regular October bulletin, APSB26-153, and needs applying on its own.
    2. Scan for the indicators of compromise above, regardless of when you patched.
    3. Rotate admin credentials and API keys as a precaution if you were running an affected version between 4 and 7 September.
    4. Review admin users created or modified since 4 September for anything you don't recognise.
    5. If you can't patch today, confirm your WAF rules are active (Sansec Shield, Cloudflare, Imperva, or Adobe's Fastly virtual patch) as a bridge, but patch as soon as you're able regardless.

    Deploy's role

    This is the third genuinely critical, unauthenticated vulnerability to hit Magento and Adobe Commerce this year, after PolyShell in July and APSB26-92 in August, and it won't be the last; we've pulled the full pattern together in our review of 2026's run of Magento zero-days. Our team had every client on an affected version patched and verified within hours of the hotfix going live on 7 September, running the indicator-of-compromise checks above on every store regardless of exploitation evidence. Out-of-hours work like that is what 2026 has demanded of anyone doing this job properly, and it's part of why Deploy's name keeps coming up alongside the other leading Magento agencies taking this year just as seriously. If you're not confident your store was checked properly during this window, talk to our support team. We'd rather confirm you're clean than have you find out the hard way.

    Need Help with Your eCommerce Project?

    Get expert advice from our Magento specialists and marketing professionals.