<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/adobe-commerce-max-severity-bug-comes-under-active-attack-kjgdofpt1" -->

---
title: Adobe Commerce max-severity bug comes under active attack
description: Adobe Commerce and Magento Open Source versions 2.4.4 through 2.4.9 are under active attack from a max-severity, unauthenticated RCE flaw dubbed StyleSmuggler...
canonical: https://daily.dev/posts/adobe-commerce-max-severity-bug-comes-under-active-attack-kjgdofpt1
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Adobe Commerce max-severity bug comes under active attack | daily.dev
og:description: Adobe Commerce and Magento Open Source versions 2.4.4 through 2.4.9 are under active attack from a max-severity, unauthenticated RCE flaw dubbed StyleSmuggler...
og:url: https://daily.dev/posts/adobe-commerce-max-severity-bug-comes-under-active-attack-kjgdofpt1
og:image: https://api.daily.dev/og/posts/KJGDoFPt1.png
og:image:alt: Adobe Commerce max-severity bug comes under active attack
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Adobe Commerce max-severity bug comes under active attack

**[CSO Online](https://daily.dev/sources/csoonline)** · 4 min read · 0 upvotes · 0 comments

## Summary

Adobe Commerce and Magento Open Source versions 2.4.4 through 2.4.9 are under active attack from a max-severity, unauthenticated RCE flaw dubbed StyleSmuggler (CVE-2026-75650, CVSS 10.0). Attackers abuse Magento's template Style properties to smuggle PHP code into the standard payment-failure reminder email, executing code when Magento renders the message, without requiring the customer to open it. Once code execution is achieved, a Rust-based backdoor is launched under disguised process names (e.g. kworker/u:8:0, fc-cache), persists via cron jobs, and communicates with a C2 server over UDP port 123 disguised as NTP traffic. Sansec, which discovered the flaw, says exploitation began September 4 and a second, unrelated attacker was already found deploying a separate PHP web shell via the same vulnerability. Adobe shipped an emergency hotfix (VULN-393411), but because attackers had a three-day window before the patch, affected stores are urged to scan for implants, check for unexpected PHP files under pub/media, and rotate credentials.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.csoonline.com/article/4219626/adobe-commerce-max-severity-bug-comes-under-active-attack.html>

## Questions this post answers

### What is the StyleSmuggler vulnerability in Adobe Commerce and Magento?

StyleSmuggler is a max-severity, unauthenticated remote code execution flaw tracked as CVE-2026-75650 with a CVSS score of 10.0, affecting Adobe Commerce and Magento Open Source versions 2.4.4 through 2.4.9. Attackers abuse Magento's template Style properties to inject malicious PHP code into the Payment Transaction Failed Reminder email, which executes when Magento renders the message, requiring no customer interaction. Adobe released emergency hotfix VULN-393411.

_Teams patching e-commerce stacks against critical CVEs like this track fixes and fallout on daily.dev._

### How does the StyleSmuggler exploit deliver its backdoor without any user interaction?

The exploit triggers Magento's standard payment-failure reminder email, and malicious PHP code injected via Style properties executes server-side while Magento renders that email, even if delivery ultimately fails. This launches a small Rust-based backdoor as a background process disguised under names like kworker/u:8:0 or fc-cache, which persists via cron jobs and communicates with a C2 server using traffic disguised as NTP over UDP port 123.

_Following exploit chains like this helps defenders spot disguised backdoors before they escalate, right on daily.dev._

### How can I tell if my Magento or Adobe Commerce store was compromised by the StyleSmuggler exploit?

Check for unexpected PHP files under the pub/media directory, since one attacker deployed a 485-byte PHP web shell inside Magento's product-image cache. Also look for suspicious background processes named kworker/u:8:0 or fc-cache, unusual cron entries scheduling restarts twice hourly, and unusual bursts of payment-failure reminder emails, then rotate credentials and secrets if any indicators are found.

_Store operators auditing for backdoors after a critical CVE can keep incident-response leads current on daily.dev._

## Similar posts on daily.dev

- [Critical BlockStrap flaw lets hackers run code on Magento servers](https://daily.dev/posts/critical-blockstrap-flaw-lets-hackers-run-code-on-magento-servers-xr6knhzgn) · BleepingComputer · 2 upvotes · 0 comments
- [Hackers exploit critical Adobe Commerce flaw to hijack customer accounts](https://daily.dev/posts/hackers-exploit-critical-adobe-commerce-flaw-to-hijack-customer-accounts-cke5dsk3l) · BleepingComputer · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#php](https://daily.dev/tags/php), [#magento](https://daily.dev/tags/magento)

[View this post on daily.dev](https://daily.dev/posts/adobe-commerce-max-severity-bug-comes-under-active-attack-kjgdofpt1)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Adobe Commerce max-severity bug comes under active attack","url":"https://daily.dev/posts/adobe-commerce-max-severity-bug-comes-under-active-attack-kjgdofpt1","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/adobe-commerce-max-severity-bug-comes-under-active-attack-kjgdofpt1"},"datePublished":"2026-09-08T11:37:10.748Z","dateModified":"2026-10-15T02:22:10.941Z","description":"Adobe Commerce and Magento Open Source versions 2.4.4 through 2.4.9 are under active attack from a max-severity, unauthenticated RCE flaw dubbed StyleSmuggler...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/cb72ca01fa74b4e8a80467b9e7d44ff9?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/cb72ca01fa74b4e8a80467b9e7d44ff9?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"CSO Online","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"CSO Online","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/98667e4b5cac46cf9c470819c6cf71cd","url":"https://daily.dev/sources/csoonline"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/adobe-commerce-max-severity-bug-comes-under-active-attack-kjgdofpt1","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,php,magento","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"CSO Online","item":"https://daily.dev/sources/csoonline"},{"@type":"ListItem","position":3,"name":"Adobe Commerce max-severity bug comes under active attack"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/adobe-commerce-max-severity-bug-comes-under-active-attack-kjgdofpt1#faq","mainEntity":[{"@type":"Question","name":"What is the StyleSmuggler vulnerability in Adobe Commerce and Magento?","acceptedAnswer":{"@type":"Answer","text":"StyleSmuggler is a max-severity, unauthenticated remote code execution flaw tracked as CVE-2026-75650 with a CVSS score of 10.0, affecting Adobe Commerce and Magento Open Source versions 2.4.4 through 2.4.9. Attackers abuse Magento's template Style properties to inject malicious PHP code into the Payment Transaction Failed Reminder email, which executes when Magento renders the message, requiring no customer interaction. Adobe released emergency hotfix VULN-393411. Teams patching e-commerce stacks against critical CVEs like this track fixes and fallout on daily.dev."}},{"@type":"Question","name":"How does the StyleSmuggler exploit deliver its backdoor without any user interaction?","acceptedAnswer":{"@type":"Answer","text":"The exploit triggers Magento's standard payment-failure reminder email, and malicious PHP code injected via Style properties executes server-side while Magento renders that email, even if delivery ultimately fails. This launches a small Rust-based backdoor as a background process disguised under names like kworker/u:8:0 or fc-cache, which persists via cron jobs and communicates with a C2 server using traffic disguised as NTP over UDP port 123. Following exploit chains like this helps defenders spot disguised backdoors before they escalate, right on daily.dev."}},{"@type":"Question","name":"How can I tell if my Magento or Adobe Commerce store was compromised by the StyleSmuggler exploit?","acceptedAnswer":{"@type":"Answer","text":"Check for unexpected PHP files under the pub/media directory, since one attacker deployed a 485-byte PHP web shell inside Magento's product-image cache. Also look for suspicious background processes named kworker/u:8:0 or fc-cache, unusual cron entries scheduling restarts twice hourly, and unusual bursts of payment-failure reminder emails, then rotate credentials and secrets if any indicators are found. Store operators auditing for backdoors after a critical CVE can keep incident-response leads current on daily.dev."}}]}
```

