Skip to content
vulnerabilityVulnerability ResearchCVE

StyleSmuggler: the zero-day with no patch and no CVE

3 min read
Share

StyleSmuggler: the zero-day with no patch and no CVE

What happened

On September 5, 2026, Dutch e-commerce security firm Sansec published research on a zero-day remote code execution vulnerability in Magento Open Source and Adobe Commerce. They named it StyleSmuggler.

Live attacks began the day before, on September 4.

As of Monday, September 7, Adobe has not issued an advisory. There is no CVE. There is no patch. Sansec's blog post is the only authoritative public source.

Why this is different from a typical zero-day

Most zero-days come with a vendor advisory, a CVE identifier, and a patch released simultaneously or shortly after disclosure. The standard advice of 'apply the vendor patch when available' breaks down when there is no patch.

StyleSmuggler also undermines the second-most-common piece of advice: keep your systems patched. The first confirmed victim was running Magento 2.4.6-p15 with both the July and August 2026 security patches fully applied. Fully patched. Compromised anyway.

The vulnerability is not in a missing patch. It is in the product itself, across all current versions.

How the attack works

Sansec reproduced the complete attack chain on clean installations of Magento 2.4.7, 2.4.8, and 2.4.9.

The exploit is unauthenticated. An attacker does not need an account on the store.

The attack unfolds in two stages that abuse Magento's own template rendering and email systems rather than a single obvious injection point. A successful attack gives the attacker code execution on the store's server and installs a persistent backdoor. Sansec has deliberately withheld specific technical details to reduce mass exploitation while Adobe prepares a response.

What you should do right now

Sansec recommends immediate server-side monitoring: review your Magento or Adobe Commerce installation for unexpected file modifications, new administrative users, and outbound connections to unfamiliar hosts.

If you use a web application firewall, contact your WAF vendor for StyleSmuggler-specific rules. Cloudflare, Fastly, and Imperva have published or are publishing signatures.

Work through Sansec's detection guide before assuming your installation is clean. Do not wait for Adobe. The absence of an official advisory does not mean the threat is not real. Adobe's most recent Commerce security bulletin dates to August 11, 2026.

The broader pattern

StyleSmuggler is not an isolated incident. E-commerce platforms have been a sustained target because they sit at the intersection of a public web interface and payment card data. Sansec tracks Magento threats as their primary research focus and their detection capabilities often precede vendor awareness.

The lesson for any organization running open-source or commercial e-commerce software is that vendor patch cycles are necessary but not sufficient. Runtime monitoring, WAF coverage, and primary-source threat intelligence need to be part of your baseline.

Gigia Tsiklauri is a Security Architect and founder of Infosec.ge. Get in touch if you need help assessing your e-commerce security posture.

Related articles