Last update:

13 October 2026

Published:

8 September 2026

StyleSmuggler – a critical vulnerability in Magento. What should you do now?

StyleSmuggler – a critical vulnerability in Magento. What should you do now?

On September 4th, someone started taking over Magento stores. Not through a weak admin password, not through a forgotten update – through a vulnerability nobody knew about just yet. StyleSmuggler (CVE-2026-75650) is a flaw in Magento that lets an attacker run their own code on your store’s server without logging in or any user interaction.

In this article you will learn:
  1. What happened?
  2. How does StyleSmuggler work?
  3. Vulnerable, compromised, data leak – these are three different things
  4. Is your store vulnerable?
  5. What to do now?
  6. The patch isn't the end of it
  7. Found traces? Don't rush the clean-up
  8. What about GDPR?
  9. How do you prepare for next time?
  10. How did we respond at Satisfly?
  11. Summary

StyleSmuggler has been given a CVSS severity score of 10.0, the highest there is. So the threat is serious. The good news is that Adobe published an official patch on September 7th, which gives us a first line of defense. But that alone may not be enough.

If your store runs on Magento Open Source or Adobe Commerce, you need to secure it IMMEDIATELY. This article will show you how.

What happened?

The first to raise the alarm was Sansec, a Dutch e-Commerce security firm. And that’s an important detail, because their team didn’t find this vulnerability during a routine audit. They found it while analyzing stores that someone had already attacked.

The first confirmed attack took place on September 4th. The first store Sansec examined had the full set of July and August security patches installed and a clean security:patch-status. Unfortunately, that wasn’t enough. The store was hacked.

A day later, on September 5th, Sansec published a warning (before it had even finished its own technical analysis). The reasoning was short: stores are being taken over right now. At that stage, the vulnerability had neither a CVE number nor an official patch.

On September 7th, Adobe released bulletin APSB26-146. StyleSmuggler was assigned the identifier CVE-2026-75650, a CVSS score of 10.0, and a priority rating of 1, the highest there is. Adobe confirmed at the same time that the flaw is being actively exploited in attacks.

The official patch appeared that same day, released as a hotfix rather than as a full platform release. That means it has to be deployed separately. Simply updating Magento to the latest version won’t solve the problem.

Pinezka

Important!

The attacks ran for several days before a patch even existed. That has serious consequences. We’ll come back to this, because it has a direct bearing on what you should do with your own store.

How does StyleSmuggler work?

A StyleSmuggler attack runs in two stages, and what makes it so elegant is that it uses nothing but mechanisms Magento already has built in.

Stage 1: poisoning the file. The attacker gets Magento to write a file containing PHP code to disk on its own. That might be a failure report in var/report/ or an entry in var/log/system.log. Nothing is executed at this stage. The code simply sits there and waits.

Stage 2: execution. The attacker triggers Magento’s built-in “Payment Transaction Failed Reminder” email. As the email template renders, the poisoned code executes.

And there are two things you need to understand here.

First, nobody has to open that email – the code runs when the message is put together, not when it’s read.

Second, the attack works even if the email never sends successfully.

The malicious code is smuggled into the template system through style properties (hence the vulnerability’s name), and that’s how it gets past existing safeguards. Adobe classifies this as server-side template injection (CWE-1336).

That CVSS score of 10.0 doesn’t come from nowhere. The attack doesn’t require a login, any permissions, or anyone to click on anything. Network access to the store is enough.

The real sleight of hand is that the attacker never had to break anything. They only had to talk the store into doing it for them.

Vulnerable, compromised, data leak – these are three different things

In the way security incidents get talked about, these three terms are constantly blurred together, and the difference between them is enormous.

A vulnerable store is one where a flaw exists and could, in theory, be exploited. Nothing more than that. If you’re running a vulnerable version of Magento and haven’t applied the patch, you’re in this category (along with tens of thousands of other stores).

A compromised store is one where traces point to successful exploitation of the vulnerability, or to an attacker’s presence in the environment. A suspicious process, a cron entry nobody added, a telltale trace in the logs – that’s this state.

A data leak means the data was genuinely read and moved outside the store’s environment.

These states don’t flow into one another automatically. The mere presence of a vulnerability doesn’t mean the store has been compromised. Finding traces of a break-in doesn’t automatically mean data has leaked.

It works the other way round too, and we need to be honest: a successful StyleSmuggler exploit lets code run with the privileges of the Magento application itself. Which means an attacker could reach everything the application has access to – store configuration, database credentials, customer and order data, integration tokens, and secrets. Once a store’s status is confirmed as “compromised”, the sensible thing is to work on the cautious assumption that this data may have made its way out of your store.

Is your store vulnerable?

If your e-Commerce store runs on:

  • Adobe Commerce 2.4.4-2026-aug to 2.4.9-2026-aug and earlier versions
  • Magento Open Source 2.4.6-2026-aug to 2.4.9-2026-aug and earlier versions
  • Adobe Commerce B2B 1.3.3 to 1.5.3 and earlier versions

… then YES. That’s the list of versions Adobe gives in bulletin APSB26-146.

In practice, this means StyleSmuggler affects nearly every Magento store out there.

And this brings us to the most uncomfortable part of the whole story. Staying on top of your updates didn’t protect anyone this time. Remember the store where Sansec first found the vulnerability? It had every available patch installed, and the built-in status check came back clean – no problems at all. The reality was something else entirely.

None of which makes regular Magento updates pointless. They’re still one of the most important things you can do for the security of your e-Commerce store. But it does tell you something: against a brand-new vulnerability, that advice can’t work by definition. Because the patch you’d be deploying simply doesn’t exist yet.

Which leaves one question: so what should you actually do?

What to do now?

1. Start with the hotfix

Adobe has already made the patch VULN-39341-composer-patches.zip available. You can download it from repo.magento.com and apply it as a composer patch, following Adobe’s instructions.

There’s one caveat. Adobe has tested this hotfix only on the 2026-aug releases listed in the bulletin. It may well work on other versions, but nobody has officially confirmed that. So before the patch goes anywhere near production, check that it’s compatible with your store and its integrations.

And if for some reason you can’t apply it straight away? Consider temporarily restricting access to GraphQL. Bear in mind, though, that this works around the problem rather than fixing it.

2. Check if the patch has actually been applied

You won’t be able to tell just by looking. Adobe recommends verifying with the Quality Patches Tool:

vendor/bin/magento-patches -n status | grep “39341\|Status”

The status should come back as Applied. If it returns anything else, the patch isn’t in place and your store is still exposed.

3. Change your encryption key and credentials

Adobe treats this as part of the fix, not as an optional extra. And rightly so, because the patch closes the door but doesn’t change the lock – and someone may already have had a key cut.

The order goes like this: enable maintenance mode, disable cron, and change the encryption key. Then work through the following one at a time:

  • the passwords of every admin panel user,
  • REST/SOAP/GraphQL integration tokens (System > Extensions > Integrations),
  • OAuth secrets for third-party applications,
  • payment gateway credentials, and do this at the provider’s end: Stripe, Braintree, Adyen, PayPal,
  • database credentials,
  • SSH and deploy keys, along with cron service accounts,
  • API keys for courier and tax integrations and any other extensions.

Finally, clear the cache, re-enable cron, and switch maintenance mode off.

Pinezka

Remember!

Rotating the encryption key on its own does not invalidate data that may already have leaked. The key encrypts integration tokens and payment gateway details, but if an attacker managed to read them, they now have them. And they couldn’t care less what key those values are encrypted with in your database. That’s why you change them at source, not just inside Magento.

The patch isn't the end of it

Applying the patch closes the vulnerability. But it doesn’t turn back the clock.

The attacks began on September 4th and are still going on today. At first because there simply was no patch. Then because plenty of stores hadn’t applied it yet. And this is where the real problem lies: what counts isn’t the date Adobe released the hotfix; it’s the date you deploy it. The time between September 4th and the fix deployment is a window in which your store stands wide open.

Adobe’s hotfix closes the vulnerability. What it doesn’t do is remove any malware that may already be sitting on your server.

The reverse holds as well. Removing malware from the server doesn’t close the vulnerability. You need both. Not one or the other.

So what should you be looking for?

  1. Suspicious processes. The malware described by Sansec hides under the name [kworker/u:8:0]. That’s the name of one of the ordinary Linux system processes, so nothing about it draws the eye in a process list. The difference is that the genuine system process of that name runs under the server’s root account and uses no memory. So if you see a [kworker/u:8:0] process running under your store’s account and consuming memory, it isn’t a system process at all. It’s an intruder. While you’re at it, check for processes named fc-cache too.
  2. Files in unusual places. The malicious file landed in the user’s home directory (~/.local/share/.gvfsd/gvfsd-user), not in the store directory. Scanning the store files alone won’t pick it up.
  3. Cron entries. Look for a job that relaunches itself every five minutes and references .gvfsd/gvfsd-user.
  4. Traces in the logs. Check both var/report/ and var/log/system.log. Confirmed infections passed through both. Look for the X_TRACE_ pattern and for a TypeError connected with the array_merge() function.
  5. An unusual flood of “Payment Transaction Failed Reminder” emails.
  6. Network traffic to the addresses Sansec listed in their advisory.

And here we have to be straight with you, because without this caveat the list above would mislead you.

First, some of the infected servers never connected back to the attackers at all. Silence on the network settles nothing.

Second, the malicious file running in memory could differ from the version written to disk. Tools that compare files and catch changes in them may simply miss it.

Third, the trace left in the logs changed over the course of the campaign. Searching for one specific string isn’t enough.

On top of that, the attackers were revising their code several times a day.

So what does that add up to? The absence of the indicators above isn’t proof that your store is clean. It’s only an absence of proof that it’s infected. And that’s quite a difference.

Found traces? Don't rush the clean-up

The instinct is a natural one: delete the cron entry, kill the process, move on. Except that in one documented case, the same malicious entry appeared 1,728 times and came back within a second of being removed.

So a sensible order of operations looks rather different.

First, preserve the evidence: logs, a filesystem image, the process list.

Only then start cleaning up.

If you have a backup from before September 4th, consider restoring the environment from it. Rotate your credentials following the list in the previous section. Go through your admin accounts and active integrations looking for changes nobody asked for. Analyze the logs from the period when the attack could have taken place. And leave extended monitoring running afterward. After the clean-up, not instead of it.

If there’s nobody on your team who works on post-breach forensics, this is the moment to bring in outside help. A server cleaned up carelessly is in a worse position than one you know is infected.

What about GDPR?

If you’ve confirmed traces of a break-in on your server, you also need to assess whether it was a personal data breach. A Magento store processes customer and order data, and a successful attack can give an attacker access to everything the application can see.

But pay attention here, because this matters. The mere fact that a server was attacked doesn’t automatically mean data leaked, or that there’s a breach you’re obliged to report. Your assessment should take into account the scope of the potential access, the type of data being processed, and what the incident analysis actually turned up.

The decision on whether to report rests with the data controller, and it should be taken together with your Data Protection Officer (if you’ve appointed one) or a legal adviser. To make that call, you need specifics: when the traces were detected, exactly what they were, and what the potential scope of access was. That information should come from your hosting provider or your technical partner (a.k.a. your e-Commerce agency).

How do you prepare for next time?

StyleSmuggler won’t be the last critical vulnerability in Magento. And that isn’t a dig at the platform. CosmicSting, SessionReaper, and a few other names make the point well enough: every popular commerce system is a target. Because behind each of them is money and card payment data.

So what separates a store that lost a few hours from a store that heard about the break-in from its payment provider a month later?

Backups you can actually restore from.
Not the ones you know are sitting somewhere.

Monitoring of files and processes, not just of whether the store is up.
In this attack, availability never dipped. The stores were running. They were selling. And they were infected the whole time.

Someone who’ll pick up the phone on a Saturday.
This vulnerability came to light on a Friday evening, and the patch arrived on the Monday evening. A support contract that runs Monday to Friday, 9 to 5, won’t be much use in that scenario.

Restricting what the store is allowed to do on the server.
For its normal day-to-day work, your store doesn’t need everything the server is capable of. Disabling unnecessary system functions, securing temporary directories, and restricting write access in the places where malware could hide and relaunch itself won’t replace the patch. But it makes it a great deal harder to turn a single attack into a permanent presence on your server.

Knowing where your keys and tokens live.
If rotating them takes three days and calls for archaeology in the documentation, then in a crisis you simply won’t do it.

How did we respond at Satisfly?

We’re not going to use this section to tell you how wonderful we are. We’ll simply describe what we’ve been doing over the past few days, because that’s probably the clearest illustration of what responding to a threat like this looks like in practice.

Right after Sansec’s warning, we extended our monitoring of Magento environments to cover the known indicators of compromise associated with StyleSmuggler. We check for suspicious processes and files on the servers, for scheduled jobs that could relaunch the malware, and for the telltale traces this particular attack leaves behind.

The monitoring runs independently in two systems.

Zabbix regularly scans the servers for known indicators and, if it detects a threat, sends the team a high-priority alert.

Wazuh provides a second, independent layer of security, running directly on the server.

Why two systems? Because a single monitoring setup that quietly stops working is worse than having none at all. It gives you the illusion of control. So we also keep an eye on the monitoring mechanism itself, to catch the moment it stops doing its job.

In parallel, we’re working on additional hardening for Magento servers – precisely what we described a few paragraphs above. Before deploying any of it, we check that it’s compatible with the specific store and its integrations. Because a safeguard that breaks the platform isn’t a safeguard at all.

And one last thing. If you run a Magento store and you don’t know whether anyone on your side is taking care of all this, now is a good moment to ask. Whoever your technology partner happens to be.

Summary

StyleSmuggler is a critical, actively exploited vulnerability that allows code to be run on your store’s server without logging in. Adobe released a patch on September 7th, and deploying it is now the single most important thing you can do. But on its own it isn’t enough.

Closing the vulnerability protects you against the next attack by that route. What it doesn’t tell you is whether anyone got in before that. So alongside the patch, you need to check your environment, and where traces of a break-in are confirmed, rotate your credentials and assess the incident from a personal data protection standpoint.

And one thing worth taking away from all this for the future. An up-to-date store is not the same thing as a secure store. StyleSmuggler proved that on a store that had every patch installed and a clean security status.

Last update:

13 October 2026

Published:

8 September 2026

In this article you will learn:
  1. What happened?
  2. How does StyleSmuggler work?
  3. Vulnerable, compromised, data leak - these are three different things
  4. Is your store vulnerable?
  5. What to do now?
  6. The patch isn't the end of it
  7. Found traces? Don't rush the clean-up
  8. What about GDPR?
  9. How do you prepare for next time?
  10. How did we respond at Satisfly?
  11. Summary

Featured Articles

Ile kosztuje sklep internetowy? - banner

How Much Does an Online Store Cost in 2025?

When you come up with the idea of creating your own e-Commerce, the first question that comes to mind is “how much all of these will cost?” This is not surprising. After all, to build a sales platform, you need to organize an appropriate budget. Unfortunately, implementing an online store is not the only cost […]

read more
Strona produktowa - banner

Product Page in e-Commerce: 9 Stores That Do It Brilliantly

The product page is one of the most important places in an online store. It is right there that the customer makes the decision: “I’m buying” or “I’m closing the tab.” Despite this, many e-Commerce businesses still treat this subpage carelessly, as just one of many, and don’t pay much attention to its UX (User […]

read more
e-commerce b2b obawy

B2B e-Commerce – dispelling your concerns

Implementing B2B e-commerce can raise many uncertainties. It’s not surprising, as it’s a project that requires business owners to remodel their operations and enter an entirely new space. That’s why many B2B trading companies hesitate to start selling online; they don’t want to bite off more than they can chew. After all, their current business […]

read more
Magento cosmetics

Cosmetics e-store on Magento – Is it a Good Idea?

Are you looking to launch your own cosmetics e-commerce? Wondering which platform to choose for your shop? There are plenty of options. But since you’ve landed on our blog, one of the solutions you might be considering is a cosmetics e-store on Magento. And that’s a great choice. Magento is one of the most efficient […]

read more

Contact us

Tell us about your e-Commerce ambitions and let us make them happen together.

Contact us
Expert Consultation

Let's talk!

Book a free consultation