Originally published February 2017. Rewritten November 2026 for current Magento Open Source and Adobe Commerce 2.4 stores. Updated November 9, 2026 with PolyShell (CVE-2026-48356). StyleSmuggler sources checked November 5 and 6, PolyShell sources November 9, 2026.
StyleSmuggler (CVE-2026-75650) is an Adobe Commerce and Magento Open Source flaw that lets an attacker run code on a store without logging in, and Adobe confirms it has been exploited. Check that Adobe's VULN-39341 hotfix is installed for your exact edition and build. The October updates (APSB26-153) are needed as well, but they do not replace the hotfix. Patching blocks new attacks. It does not remove an earlier compromise.
There's a second exploited flaw to check. PolyShell (CVE-2026-48356) is a file upload flaw that CISA added to its list of actively exploited vulnerabilities on October 27, 2026. Adobe fixed it in July (APSB26-73). If your store doesn't have the July 2026 fixes yet, it is exposed to both.
| Where you are | What to do next | Source |
|---|---|---|
| You don't know whether the hotfix is installed | Ask your maintainer for installation evidence for your build (see priority 1) | Adobe APSB26-146 KB |
| You don't know whether the July 2026 fixes (PolyShell) are installed | Ask for your exact build and the monthly patches applied since July (see priority 1) | Adobe APSB26-73 |
| Hotfix confirmed, credentials rotated, no signs of compromise | Keep monitoring and keep patching. This is a good position, not a guarantee | Adobe APSB26-146 KB |
| Something looks wrong, or the store was unpatched during the attack window | Start a security-led incident response, then complete patching and credential rotation | Imperva, Nov 2, 2026 |
StyleSmuggler: what merchants need to know now
StyleSmuggler isn't a new November vulnerability. Adobe released security update APSB26-146 on September 7, 2026. Adobe says it is aware that CVE-2026-75650 "has been exploited in the wild targeting Adobe Commerce merchants." In Adobe's words, the flaw "could allow an unauthenticated attacker to execute arbitrary code on an affected installation."
What's new is the reporting on what attackers did with it. On November 2, 2026, Imperva published research on a campaign that ran from September 9 to 13. It hit Magento and Adobe Commerce stores in Western Europe, North America and Asia-Pacific. The attackers installed a remote access trojan that Imperva tracks as PSK Agent. In some cases they also left a PHP webshell, which gave them a second way back in. Cybersecurity News summarized that research on November 3. Imperva also notes that several attacker groups have used the same flaw to deliver different malware.
So the fix has been out since September. But a store that was exposed before it was patched may still carry something an attacker left behind.
PolyShell: the second exploited flaw
PolyShell is the name security firm Sansec gave to CVE-2026-48356. Adobe classifies it as an unrestricted upload of a file with a dangerous type. It rates the flaw as Critical and says no authentication is needed to exploit it. Adobe's bulletin gives a CVSS score of 9.6. The NVD record lists 9.3. The CVE description says it "could result in arbitrary code execution in the context of the current user."
According to Sansec, attackers send a file through the guest cart REST API that passes as an image but also contains PHP code. Magento saves it in pub/media/custom_options/quote/. Whether that file can run depends on the web server configuration. Where it can't, Sansec notes the file still stays on disk. A later configuration change could expose it.
Adobe released the fix in bulletin APSB26-73 on July 14, 2026. That bulletin, last updated August 11, still says Adobe is not aware of exploits. CISA sees it differently. On October 27, 2026 it added CVE-2026-48356 to its Known Exploited Vulnerabilities catalog. CISA only does that on evidence of active exploitation. Sansec reports attacks from March 19, 2026, months before Adobe's fix. It describes uploaded webshells, a backdoor called accesson.php copied into many folders, and JavaScript injected into CMS pages and blocks.
Adobe lists these versions as affected:
- Adobe Commerce: 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15, 2.4.5-p17, 2.4.4-p18 and earlier. Fixed in the matching 2026-jul builds, for example 2.4.8-2026-jul.
- Magento Open Source: 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15 and earlier. Fixed in 2.4.9-2026-jul to 2.4.6-2026-jul.
- Adobe Commerce B2B and Adobe Commerce Events (1.6.0 to 1.20.0, fixed in 1.21.0).
Sansec says the 2.4.9 release already contained the fix, but Adobe's bulletin lists 2.4.9 as affected. Follow Adobe and make sure 2.4.9 stores have the July fixes too.
Is my store affected?
Adobe's bulletin lists affected versions for Adobe Commerce (the 2.4.4 to 2.4.9 lines, up to and including the 2026-aug releases), Adobe Commerce B2B, and Magento Open Source (the 2.4.6 to 2.4.9 lines). The hotfix differs by build, so the answer depends on three things:
- Edition: Magento Open Source, Adobe Commerce on-premises, or Adobe Commerce on Cloud.
- Exact build: for example 2.4.7-p8 or 2.4.8-2026-aug, not just "2.4.7".
- Patch evidence: whether the matching VULN-39341 patch file is installed and active in production.
Treat Adobe's live version table as the authority. Have a Magento engineer match your build to the right row. Adobe's intro sentence about compatible versions doesn't read exactly like its detailed table. So don't rely on a summary, including this one.
If your store runs a version that isn't in Adobe's tables, such as an old 2.3 build or Magento 1, there's no listed hotfix to apply. Imperva's advice is that unsupported branches need vendor-supported remediation or a migration plan.
Patched is not the same as clean
Imperva puts it plainly: applying the VULN-39341 hotfix "closes the initial StyleSmuggler entry point, but it does not remove a RAT, webshell, stolen credentials, or other persistence established before patching."
That leaves two questions. Was the store exposed between the disclosure and the moment the hotfix went live? And has there been any sign of activity since then? If the answer to either one is "yes" or "we don't know," treat it as a possible incident (priority 2), not just a patching task.
The same goes for PolyShell. Sansec saw attacks from March, and Adobe's fix came in July. A store patched in July can still hold files uploaded before then.
1. Verify patches, including the separate hotfix
Three Adobe bulletins matter here, and they do different jobs:
- APSB26-73 (July 14) fixes PolyShell, along with other issues, in the 2026-jul builds.
- APSB26-146 (September 7) fixes StyleSmuggler with the VULN-39341 hotfix and tells you to rotate your encryption keys.
- APSB26-153 (October 13) fixes a separate set of critical and high-severity issues. Adobe says it knows of no exploits for the issues in that bulletin. It also says: "Please apply the Hotfix for CVE-2026-75650 in addition to the security updates released in this bulletin."
That last point is the one to check. An installed October update doesn't prove StyleSmuggler is fixed. Adobe itself notes that "it isn't possible to easily determine if the issue was patched," which is why you need confirmation.
Adobe publishes a confirmation method that uses its Quality Patches Tool, documented for Adobe Commerce on Cloud. For on-premises and Open Source stores, your engineer should run the equivalent check for the way patches are applied in your deployment. Follow Adobe's instructions, not commands copied from a blog.
Patch order
Adobe's October patch article explains how the monthly fixes stack up:
- Latest -p release first. Isolated security patches are tested only against the latest security-only patch release (the latest -p version) for your release line, so the store needs to be on it.
- Every monthly isolated patch, in order. Each month's patch builds on the previous one, so all earlier monthly patches for your line have to be in place before the current one. The PolyShell fix arrived with the July 2026 patches. On Adobe Commerce on Cloud, the latest cloud-patches update already contains the fix. Adobe warns that applying the isolated patch on top of it can make the installation fail.
- The StyleSmuggler hotfix, separately. Adobe says the CVE-2026-75650 hotfix "is not included in the October Isolated patch file" and "must be applied separately."
For the monthly patches, Adobe now recommends its Commerce Version Tool. It ships with the July 2026 isolated patch and reports which monthly patches are applied, which are missing, and per-CVE status. Your engineer should still confirm VULN-39341 on its own.
As of November 9, 2026, we found no confirmed new Adobe Commerce security release after APSB26-153. Don't wait for one.
Ask your maintainer for these records
- The installed edition and exact build in production.
- Which VULN-39341 patch file was applied, and its status (Adobe's tool reports "Applied").
- The date and time the patch reached production, not just staging.
- Whether the July 2026 fixes (APSB26-73, PolyShell) and every later monthly patch, including APSB26-153, are installed, and the relevant release notes.
- Whether credential rotation was completed (priority 3), and when.
- Results of a checkout and integration smoke test after deployment.
A clear written answer to these points tells you more than "we're up to date."
2. Investigate suspected compromise
If the store was exposed or anything looks off, bring in your hosting provider and a security responder before anyone deletes files. Preserve web, application and server logs. Deleting a suspicious file can wipe the evidence you need to find out what else was touched. It may also leave the attacker's other footholds in place.
The responder decides on containment: take the store offline, isolate the server or restore from a known-good state. Imperva advises that systems with any campaign indicator "should be treated as potentially fully compromised and investigated accordingly."
Signals worth escalating
These come from Imperva's research. They're reasons to escalate, not a complete checklist:
- Unexpected PHP files in public folders such as
pub/media/or the Magento root. - Unknown processes, including ones named to look like normal Linux processes.
- New scheduled jobs (cron or system services) nobody added.
- The web server making unexpected outbound connections or DNS lookups.
For PolyShell, Sansec and TrendAI add these checks:
- Any file other than a genuine image in
pub/media/custom_options/. Sansec treats a.php,.phtmlor.pharfile there as a strong sign of compromise. - Files named
accesson.php, often inassets/images/folders created inside other directories. - Scripts you don't recognize in CMS pages, static blocks or the checkout.
- New files in
var/report/, which TrendAI links to StyleSmuggler. - A web server that will execute PHP from
pub/media/or other upload folders. Your engineer should block that. Sansec warns it limits the damage but doesn't stop uploads.
If any of these turn up, priority 3's rotation applies to you as well.
Imperva's and Sansec's posts list specific file names and network indicators for these campaigns. Not finding them doesn't prove a store is clean, because other attackers used different tools. That judgment belongs to the incident responder.
3. Rotate exposed keys and credentials properly
Adobe tells merchants to rotate "not only your encryption key but all credentials that may have been encrypted or exposed using it." The encryption key protects integration tokens, payment gateway credentials and automation tokens. Rotating it doesn't invalidate secrets that may already have been copied.
Adobe's documented sequence includes these steps, in order: apply the hotfix, enable maintenance mode, disable cron, rotate encryption keys, then rotate Admin passwords, REST/SOAP/GraphQL integration tokens, OAuth client secrets, payment gateway API credentials, database and Fastly/CDN credentials (via support ticket, per Adobe), SSH and deploy keys, service accounts, and API keys for shipping, tax and other extensions. Then flush the cache, re-enable cron and leave maintenance mode.
Payment, shipping and tax credentials must be rotated at the provider, not just inside Magento. Plan this as a maintenance window with an engineer who knows every integration on the store. A missed key means a broken checkout or an integration that stops syncing.
4. Secure administrator access
Adobe Commerce and Magento Open Source require two-factor authentication for Admin sign-in, with providers such as Google Authenticator, Duo and hardware keys. Keep it on for every account. Beyond that:
- Give each person their own account with only the roles they need.
- Remove accounts for former staff and agencies.
- Restrict who can reach the Admin, for example by IP allowlisting at the hosting or firewall level, set up by your engineer.
These controls matter, but neither StyleSmuggler nor PolyShell needs a login. Strong Admin security doesn't replace the hotfix.
5. Protect integrations and secrets
The 2017 version of this article suggested writing passwords on a sticky note. Don't. Use a password manager for people and a proper secret store for system credentials.
Keep an inventory of every integration: ERP, PIM, payment, shipping, marketing and analytics. For each one, write down who owns it, which token it uses, what rights it has and where to rotate it. With that list, priority 3 becomes a planned job instead of a scramble. It also shows you which tokens nobody uses anymore, so you can remove them.
6. Maintain extensions, runtime and supported versions
Every store needs a named owner for updates, either in-house or at your agency. That person tracks Adobe's security bulletins, keeps extensions and the server stack updated, and removes modules that are no longer maintained. Before a security release goes live, test it in staging against each of your extensions. We're not listing compatible versions here, because that depends on your build.
If you're on a release line that's close to the end of support, plan the upgrade path now, not after the next urgent bulletin.
7. Use HTTPS and layered monitoring
Serve the whole store over HTTPS. That protects data in transit. On its own, it doesn't make a store PCI DSS compliant, and it does nothing against a flaw like StyleSmuggler.
A web application firewall, file-integrity monitoring and alerts on unusual outbound traffic add useful layers. Imperva reported that the PSK Agent dropper had a 0% detection rate on VirusTotal at the time of their analysis (SHA-256 published in their IOC table). File reputation alone is not enough. These are extra layers. They don't replace patching.
8. Test backups and recovery
A backup you've never restored is a hope, not a plan. Test that you can restore the code, database and media to a clean environment. Then check checkout, payments and integrations.
Decide in advance who leads an incident: who calls the host, who contacts the payment provider, who decides on taking the store offline, and who informs customers if it comes to that. Write it down before peak season.
Next step
Want a second pair of eyes on your patch evidence, credential rotation plan or upgrade path? Our team handles ecommerce development and maintenance for Magento stores. We'll tell you what we find, including when everything is fine.
Sources (StyleSmuggler checked November 5, 2026. PolyShell and Adobe patch article checked November 9, 2026)
- Adobe, Urgent Action Required: Critical Security Update Available for Adobe Commerce (APSB26-146), last updated September 21, 2026: https://experienceleague.adobe.com/en/docs/commerce-knowledge-base/kb/announcements/commerce-apsb26-146
- Adobe, Security update available for Adobe Commerce, APSB26-153, October 13, 2026: https://www.adobe.com/trust/security/products/commerce/apsb26-153.html
- Adobe, Security update available for Adobe Commerce, APSB26-73, July 14, 2026, last updated August 11, 2026: https://www.adobe.com/trust/security/products/commerce/apsb26-73.html
- Adobe, Security update available for Adobe Commerce - APSB26-153 (patch article), last updated October 16, 2026: https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-49323
- CISA, Known Exploited Vulnerabilities Catalog, CVE-2026-48356, added October 27, 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-48356
- NIST NVD, CVE-2026-48356: https://nvd.nist.gov/vuln/detail/CVE-2026-48356
- Adobe, Two-factor authentication (2FA), last updated October 8, 2026: https://experienceleague.adobe.com/en/docs/commerce-admin/systems/security/2fa/security-two-factor-authentication
- Imperva (Daniel Johnston, Gabi Sharadin), StyleSmuggler Exploitation Deploys PSK Agent RAT Against Magento Stores, November 2, 2026: https://www.imperva.com/blog/stylesmuggler-exploitation-deploys-psk-agent-rat-against-magento-stores/
- Sansec Forensics Team, PolyShell: unrestricted file upload in Magento and Adobe Commerce, March 17, 2026 (with later updates): https://sansec.io/research/magento-polyshell
- Sansec Forensics Team, Mass PolyShell attack wave hits 471 stores in one hour, March 30, 2026: https://sansec.io/research/polyshell-mass-attack-wave
- TrendAI Research, Two Ways In Before the Holiday Rush: Exploited Adobe Commerce Flaws Put Online Stores at Risk, November 6, 2026: https://www.trendaisecurity.com/en-us/resources-insights/trendai-security-blog/two-commerce-flaws-put-online-stores-at-risk
- Cybersecurity News (Tushar Subhra Dutta), Hackers Exploit Adobe Commerce Zero-Day to Deploy PSK Agent RAT and Remotely Control Servers, November 3, 2026: https://cybersecuritynews.com/adobe-commerce-zero-day/
Frequently asked questions
What is StyleSmuggler? StyleSmuggler is the name for CVE-2026-75650, an Adobe Commerce and Magento Open Source vulnerability that lets an unauthenticated attacker execute code on an affected store. Adobe fixed it with the VULN-39341 hotfix in bulletin APSB26-146 and confirms it was exploited.
What is PolyShell? PolyShell is Sansec's name for CVE-2026-48356, a file upload flaw in Adobe Commerce and Magento Open Source. Adobe fixed it in APSB26-73 in July 2026. CISA added it to its list of exploited vulnerabilities on October 27, 2026.
Is this a new November vulnerability? No. Adobe released the fix on September 7, 2026. The November news coverage is about Imperva's research into a September attack campaign.
Does APSB26-153 include the StyleSmuggler fix? No. Adobe's October bulletin says to apply the CVE-2026-75650 hotfix in addition to its own updates.
In what order do we patch? Get onto the latest -p release for your line, apply every monthly isolated patch in order (PolyShell is fixed from July onward), and install the StyleSmuggler hotfix separately. Your engineer follows Adobe's instructions for your edition.
How do I check without attacking my own store? Ask your engineer to confirm the installed patch status using Adobe's documented method for your edition. Don't test production by trying to exploit it.
Will patching remove malware that's already there? No. Patching closes the entry point. A remote access tool, webshell or stolen credentials need incident response.
Is rotating the encryption key enough? No. Adobe says to rotate all credentials that may have been exposed, at their source. That includes payment gateway, integration, database and SSH credentials.
Can a firewall, HTTPS or 2FA replace the hotfix? No. They're useful layers, but the hotfix is the fix.
Should we wait for Adobe's next scheduled release? No. The fixes for both flaws are available now. As of November 9, 2026, we found no confirmed new Adobe Commerce security release. A future release is no reason to wait.



