CVSS 10.0
Maximum possible severity: CVE-2026-75650 requires no authentication, no user action, and affects every Adobe Commerce and Magento 2.4.4 through 2.4.9 installation including fully patched stores
3 days
Duration that active StyleSmuggler exploitation ran before Adobe released Hotfix VULN-39341, from confirmed first attack on September 4 to the patch on September 7, 2026
2.4.4 to 2.4.9
Full version range affected by CVE-2026-75650, covering every Adobe Commerce and Magento Open Source release since 2022, regardless of prior security update status
8 credential classes
Categories requiring rotation after a StyleSmuggler compromise: admin passwords, REST/SOAP/GraphQL tokens, OAuth secrets, payment gateway API keys, database credentials, SSH keys, deploy keys, and extension API keys

SponsoredHorizon3.ai

Proactive Security for the AI Era

NodeZero continuously and autonomously pentests infrastructure, identity, cloud, and now web applications, chaining weaknesses across every domain the way real attackers do. Every finding ships with replayable proof showing exploitable business impact, not theoretical risk.

See NodeZero WebApp in action

CVE-2026-75650, the zero-day vulnerability named StyleSmuggler, gave unauthenticated attackers remote code execution on every Adobe Commerce and Magento 2.4.4 through 2.4.9 installation for 72 hours before Adobe issued any patch, with multiple victim stores confirmed backdoored across distinct attack campaigns. Sansec, which discovered the vulnerability, observed first exploitation on September 4, 2026. Adobe released Hotfix VULN-39341 under security bulletin APSB26-146 on September 7. CISA added CVE-2026-75650 to its Known Exploited Vulnerabilities catalog on September 8, 2026.

Adobe Commerce Magento zero-day RCE via CVE-2026-75650 exploits a critical flaw in how Magento processes the styles property of its email template system. An attacker sends a crafted HTTP request that injects PHP code into a template variable without any authentication requirement. The injected code remains dormant until the store's background job queue processes the next failed-payment email notification, at which point the code executes under the web server's process context. The attack requires no valid account, no session token, and no user to open a malicious link.

Every store in the affected version range is a live target if VULN-39341 has not been applied. Stores compromised before patching cannot be cleaned by applying the hotfix alone. StyleSmuggler drops two persistent implants: a Rust-compiled backdoor that impersonates a system daemon and communicates over NTP-disguised traffic, and a PHP web shell in the Magento media directory for interactive access. Both survive a patch update. Merchants must treat any store that was internet-accessible during the September 4 to September 7 window as potentially compromised and conduct a full incident response before trusting the environment.

How Does StyleSmuggler Work?

StyleSmuggler targets Magento's email template rendering pipeline. Adobe Commerce and Magento Open Source include a template engine that evaluates variables embedded in template markup, including the styles property that controls CSS styling injected into generated emails. The styles field passes through a PHP parsing path that does not apply sufficient sanitization before evaluation.

An unauthenticated attacker sends a single HTTP POST request to the Magento endpoint responsible for email template configuration. The request sets the styles parameter to a PHP code string. Because authentication is not required at this processing step, the injected code is stored in the template's database record or evaluated in memory against the next render cycle.

Magento runs background cron jobs to process queued email notifications, including failed-payment alerts triggered by any checkout session. When the next failed-payment event occurs, the store's PHP-FPM worker renders the payment email template, evaluating the attacker's injected styles value as PHP code in the process. The execution context is the web server user, typically www-data or nginx, providing access to the store's database credentials, encryption keys, and the entire webroot filesystem.

The attack chain does not require any administrative login, any customer account, or any application session. An attacker targeting a large store can trigger the execution phase by initiating an abandoned checkout on a test product. On busy merchant sites, the background queue runs every few minutes, triggering execution automatically without attacker interaction after the initial injection request.

1

Unauthenticated Template Injection

Attacker sends a crafted HTTP POST to the Magento email template endpoint with PHP code embedded in the styles parameter. No credentials or session required.

2

Code Stored in Template Record

Injected PHP is stored in the store's database as part of the email template configuration, persisting until the template is purged or overwritten.

3

Cron Queue Triggers Execution

Magento's background cron job processes the email queue. When a failed-payment event fires, PHP-FPM renders the email template and executes the injected code under the web server user context.

4

Rust Backdoor and PHP Web Shell Dropped

The executed payload writes a Rust-compiled binary to disk, masquerading as a system daemon, and drops a PHP web shell in the Magento media directory for persistent interactive access.

5

Stealthy C2 via NTP-Mimicking Traffic

The Rust backdoor initiates outbound connections on port 123 with traffic structured to resemble NTP time-sync requests, bypassing firewall rules that permit NTP outbound from servers.

Which Adobe Commerce and Magento Versions Are Affected by CVE-2026-75650?

CVE-2026-75650 affects every version of Adobe Commerce and Magento Open Source from 2.4.4 through 2.4.9, including Adobe Commerce B2B 1.3.3 through 1.3.9. The vulnerability exists in the core template rendering architecture shared across all versions in this range, which means prior security updates to individual components did not remediate the flaw.

Merchants running cloud-hosted Adobe Commerce on Adobe's managed infrastructure received automatic patches through Adobe's cloud deployment pipeline following the September 7 hotfix release. On-premises merchants and those running hybrid or private cloud deployments must apply VULN-39341 manually.

Magento Open Source 2.4.4 and 2.4.5 reached end-of-life and do not receive Adobe's official hotfix. These versions should be treated as permanently vulnerable unless merchants upgrade to a supported version in the 2.4.6-2.4.9 range where the patch applies.

There are no architectural or configuration mitigations that eliminate the attack surface without applying VULN-39341. Disabling failed-payment email notifications reduces the automatic trigger path but does not prevent an attacker from injecting code and manually triggering execution through other queue events. WAF rules targeting the injection pattern provide detection and blocking capability for known attack signatures but cannot guarantee protection against obfuscated variants.

Free daily briefing

Briefings like this, every morning before 9am.

Threat intel, active CVEs, and campaign alerts, distilled for practitioners. 50,000+ subscribers. No noise.

What Payloads Does StyleSmuggler Deploy?

CVE-2026-75650 deployments confirmed during active exploitation carry two distinct implants that provide complementary persistence and access mechanisms.

The primary payload is a Rust-compiled binary. Rust executables are increasingly common in attacker toolkits because they produce small, self-contained binaries with no dependency requirements and no external libraries that endpoint detection tools can flag by filename or hash alone. The backdoor copies itself to a path that mimics a legitimate system daemon name and registers persistence to restart on process death. Its command-and-control communication runs over port 123 with traffic patterned to resemble NTP time-synchronization messages, exploiting the near-universal firewall rule that permits NTP outbound from servers.

The secondary payload is a PHP web shell dropped into Magento's /pub/media/ directory. This directory is served by the web server without PHP execution restrictions in default configurations. The media directory is intended for uploaded images, PDFs, and downloadable products. In standard Apache and Nginx configurations, PHP files in this directory execute normally unless the server has been explicitly configured to disable PHP in media paths. The web shell provides interactive HTTP-based command execution alongside the C2 channel maintained by the Rust backdoor.

Critically, the patch alone does not remove either implant. VULN-39341 modifies the template rendering pipeline to block the injection path, but leaves any files already written to disk and any database records already modified. Merchants who applied the patch without first scanning for compromise may have a fully patched store hosting an active backdoor. Review the IOCs in this post and run a full forensic scan before declaring remediation complete.

Subscribe to unlock Indicators of Compromise

Free subscribers unlock full IOC lists, Sigma detection rules, remediation steps, and every daily briefing.

Sigma Detection Rules for CVE-2026-75650 StyleSmuggler

Two rules target the critical execution and C2 phases of CVE-2026-75650 StyleSmuggler exploitation. Both carry status: experimental. Validate against your environment before production deployment.

Shell spawn detection: PHP-FPM or web server workers spawning unexpected shell processes, the direct indicator of successful template injection code execution.

  • Log sources: Linux audit, auditd, or sysmon-for-linux process creation telemetry from web server hosts

C2 channel detection: Outbound port 123 connections from web server process accounts to hosts outside your approved NTP server list. The StyleSmuggler Rust backdoor uses this as its primary C2 path.

  • Log sources: Host-based network telemetry (Linux auditd with SYSCALL, sysmon-for-linux, or EDR agent network events)

Subscribe to unlock Sigma Detection Rules

Free subscribers unlock full IOC lists, Sigma detection rules, remediation steps, and every daily briefing.

Subscribe to unlock Sigma Hunt Queries

Free subscribers unlock full IOC lists, Sigma detection rules, remediation steps, and every daily briefing.

Subscribe to unlock WAF Detection Rules

Free subscribers unlock full IOC lists, Sigma detection rules, remediation steps, and every daily briefing.

How to Patch CVE-2026-75650 and Remediate a Compromised Store

Adobe released Hotfix VULN-39341 under security bulletin APSB26-146 on September 7, 2026. Apply the patch and complete a full compromise assessment before returning any store to production. VULN-39341 closes the injection path but does not clean an already-compromised environment.

For stores accessible during the September 4 to September 7 window, assume compromise and investigate before returning to production. CISA's KEV catalog listing confirms active exploitation, and multiple distinct attack groups operated during this window. The following steps address both the patch and post-compromise hygiene.

Apply official patch →helpx.adobe.com/security/products/magento/apsb26-146.html

Subscribe to unlock Remediation & Mitigation steps

Free subscribers unlock full IOC lists, Sigma detection rules, remediation steps, and every daily briefing.

Why StyleSmuggler Matters for Your Organization

CVE-2026-75650 represents the highest-impact e-commerce platform vulnerability in recent years. Adobe Commerce and Magento power a significant portion of global e-commerce infrastructure, and a compromised store exposes not just the merchant but every customer whose payment data and credentials pass through it. The attacker does not need to breach a firewall or guess a password; the entire attack begins and ends via an HTTP POST request to a standard web endpoint.

The StyleSmuggler attack chain is notable for two structural characteristics that extend beyond this specific CVE. First, execution is deferred: the attacker injects code and then waits for the store's own background process to trigger it. This deferred execution pattern evades signature-based WAF rules that monitor request payloads in real time. The injection request itself may appear to be a legitimate template modification, with the malicious PHP code embedded inside a CSS-like parameter value.

Second, the Rust backdoor's NTP-mimicking C2 channel is designed to bypass the most common outbound firewall rule in server environments. NTP is almost universally permitted outbound from servers, and most organizations do not inspect UDP/TCP port 123 traffic beyond verifying it reaches known time servers. The backdoor exploits this assumption to establish a persistent C2 channel that survives standard firewall review.

For organizations managing customer-facing web applications running PHP frameworks, CVE-2026-75650 reinforces two controls that reduce exposure across vulnerability classes: enforcing strict execution policies in file upload directories (the media directory in Magento should never execute PHP), and deploying network-layer monitoring for unexpected outbound connections from web server processes. Both controls would have detected this attack pattern regardless of whether the specific CVE was known.

Defenders managing web application infrastructure should also review the CVE-2026-81578 PaperCut pre-auth RCE analysis, which demonstrated a similar deferred-execution pattern in a different application framework, and the CVE-2026-19490 Citrix NetScaler auth bypass post, which covered the same class of pre-authentication RCE impact on perimeter infrastructure.

The bottom line

Adobe Commerce Magento zero-day RCE via CVE-2026-75650 StyleSmuggler compromised multiple stores during a 72-hour window before any patch existed. Apply VULN-39341 from APSB26-146 immediately. Scan /pub/media/ for PHP web shells, query the email_template database table for injected styles containing eval or base64_decode, and check for unexpected port 123 outbound connections from your web server processes to non-NTP external hosts. Any store accessible between September 4 and 7 must be treated as potentially compromised. Rotate all eight credential classes after generating a new encryption key with bin/magento magento:encryption:key:change before end of day.

This analysis is generic. create a free account to score threats like this against your own stack.

Frequently asked questions

What is StyleSmuggler (CVE-2026-75650)?

StyleSmuggler is the name given to CVE-2026-75650, a CVSS 10.0 zero-day remote code execution vulnerability in Adobe Commerce and Magento Open Source. It allows an unauthenticated attacker to inject malicious PHP code through the styles property in Magento's email template system. When the store renders a failed-payment notification, the injected code runs under the web server's user context, giving the attacker full code execution without any login credentials or user interaction. Adobe issued Hotfix VULN-39341 under security bulletin APSB26-146 on September 7, 2026, after active exploitation was already confirmed for three days.

Which Adobe Commerce and Magento versions are affected by CVE-2026-75650?

CVE-2026-75650 affects Adobe Commerce 2.4.4 through 2.4.9, Adobe Commerce B2B 1.3.3 through 1.3.9, and Magento Open Source 2.4.6 through 2.4.9. Adobe Commerce and B2B versions 2.4.4 and 2.4.5 require standalone ZIP patches because composer patch format is not supported on those older versions. Magento Open Source 2.4.4 and 2.4.5 are end-of-life and do not receive VULN-39341. Cloud merchants on Adobe Commerce on Cloud Infrastructure received automatic patches via Adobe's managed deployment pipeline.

How does CVE-2026-75650 StyleSmuggler work technically?

StyleSmuggler exploits a flaw in Magento's email template rendering pipeline. The styles property of email templates passes through a PHP evaluation path without sufficient sanitization. An unauthenticated attacker sends a crafted HTTP request that sets the styles value to executable PHP code. No login is required because the vulnerable endpoint does not enforce authentication before processing the template parameter. When the store's background cron job processes the next failed-payment event, the injected PHP executes under the web server's process context with full access to the database, encryption keys, and webroot filesystem.

Is my store vulnerable if I applied all security patches before CVE-2026-75650?

Yes. CVE-2026-75650 is a zero-day present in every version of Adobe Commerce and Magento Open Source from 2.4.4 to 2.4.9, including stores that applied every prior security update. The flaw exists in the base template rendering architecture, not in a component addressed by earlier patches. Sansec confirmed that multiple stores running fully updated software were successfully backdoored during the active exploitation window from September 4 to September 7, 2026.

How do I detect if my Magento store was compromised by StyleSmuggler?

Scan your Magento media directory for PHP files using: find /pub/media -name '*.php' -type f. Check for recently modified PHP files across the entire webroot: find . -name '*.php' -newer var/log/system.log -type f. Look for unexpected outbound connections on port 123 from your web server process using: netstat -anp | grep :123. Review web server access logs for POST requests to template-handling endpoints with base64-encoded or eval-containing payloads. Query the email_template database table: SELECT template_id, template_code, template_styles FROM email_template WHERE template_styles LIKE '%eval%' OR template_styles LIKE '%base64%'. Sansec's eComscan tool provides StyleSmuggler-specific automated detection.

Does the VULN-39341 patch remove an existing StyleSmuggler backdoor?

No. VULN-39341 patches the template injection flaw to prevent new infections but does not scan for or remove existing backdoors or web shells. Any store compromised before applying the patch requires a full incident response: scan the webroot and media directory for PHP files that do not belong, check for Rust binaries running as system-like process names, audit all database tables for injected content, rotate all credentials, and restore from a clean backup if compromise is confirmed. Adobe's security bulletin explicitly states that compromised merchants must treat the store as fully owned.

What credentials do I need to rotate after a StyleSmuggler compromise?

Adobe's remediation guidance requires rotating eight credential classes: admin panel passwords, REST API integration tokens, SOAP API tokens, GraphQL integration tokens, OAuth client secrets, payment gateway API credentials (Stripe, Braintree, PayPal, and others), database usernames and passwords, and SSH deploy and access keys. Extension API keys should also be rotated because extensions often store credentials in Magento's encrypted configuration, which is protected by the Commerce encryption key. Rotate the encryption key first using the bin/magento magento:encryption:key:change command, then update all downstream credentials that were protected by the old key.

How do I apply the Adobe Commerce VULN-39341 patch?

Download VULN-39341-composer-patches.zip from Adobe's repo.magento.com authenticated repository. For on-premise Adobe Commerce 2.4.6-2.4.9: run composer require magento/quality-patches and apply via the Magento Quality Patches tool. For Adobe Commerce 2.4.4 and 2.4.5: use the standalone ZIP patch format. Run bin/magento setup:upgrade and bin/magento cache:flush after applying. Cloud merchants should run ece-patches apply to pull the latest cloud patch bundle. Adobe Commerce B2B merchants must patch both the Commerce base and the B2B module separately using the corresponding hotfix files from APSB26-146.

Sources & references

  1. Adobe Security Bulletin APSB26-146
  2. Sansec: StyleSmuggler Magento and Adobe Commerce 0-day RCE (CVE-2026-75650) under active attack
  3. BleepingComputer: Adobe fixes critical Magento zero-day exploited to backdoor servers
  4. CISA Known Exploited Vulnerabilities Catalog: CVE-2026-75650
  5. Tenable: StyleSmuggler CVE-2026-75650 Frequently Asked Questions

Free resources

25
Free download

Critical CVE Reference Card 2025–2026

25 actively exploited vulnerabilities with CVSS scores, exploit status, and patch availability. Print it, pin it, share it with your SOC team.

No spam. Unsubscribe anytime.

Free download

Ransomware Incident Response Playbook

Step-by-step 24-hour IR checklist covering detection, containment, eradication, and recovery. Built for SOC teams, IR leads, and CISOs.

No spam. Unsubscribe anytime.

Free newsletter

Get threat intel before your inbox does.

50,000+ security professionals read Decryption Digest for early warnings on zero-days, ransomware, and nation-state campaigns. Free, daily, no spam.

Unsubscribe anytime. We never sell your data.

Eric Bang
Author

Founder & Cybersecurity Evangelist, Decryption Digest

Cybersecurity professional with expertise in threat intelligence, vulnerability research, and enterprise security. Covers zero-days, ransomware, and nation-state operations for 50,000+ security professionals every morning.

Giveaway: InfoSec World 2026 All Access Pass ($3,895 value)

Details →
Daily Briefing

Subscribe to enter the giveaway

Every subscriber is automatically entered. You also get daily threat intel every morning: zero-days, ransomware, and nation-state campaigns. Free. No spam.

Already subscribed? You're already entered.

Giveaway

Win a $3,895 InfoSec World 2026 pass.