CVE-2026-75650Active Exploitation(adobe / commerce)

CRITICALCVSS 10.0 · CRITICALCISA KEV

Exploitation observed; activity peaked at 69 mentions and remains active

Immediate actions

  • Patch adobe commerce systems immediately
  • Assume compromise if assets are exposed
  • Hunt for exploitation attempts and persistence artifacts
  • Increase monitoring for publicly documented tradecraft

Recommended action window: Immediate (within 24h)

NVD description

Adobe Commerce is affected by an Improper Neutralization of Special Elements Used in a Template Engine vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction. Scope is changed.

8.5/ 10 priority

Sources & remediation

Listed in the CISA Known Exploited Vulnerabilities catalog. Federal remediation due date: 2026-09-11. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Weakness type (CWE)
CWE-1336

Priority

CRITICAL

Exploitation

ACTIVE

PoC

YES

Patch

AVAILABLE

Momentum

DECLINING

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • commerce
  • commerce_b2b
  • magento

Threat summary

  • Active exploitation appears in 121 classified signals
  • Public PoC and exploit tooling are both present
  • Patch or workaround signal is available
  • 180 mentions across 25 observed days

What's happening

  • Active exploitation reported across 121 signals
  • Exploit tool or code specified in 10 signals
  • PoC mentioned or linked in 24 signals
  • Patch or workaround mentioned in 111 signals
  • Technical details provided in 128 signals
  • General: 13 classified signals
  • Peaked 23d ago at 69 mentions (2026-09-08); latest day: 1
  • 180 total mentions across 25 days

Affected systems

Vendors
Products
commercecommerce_b2bmagento

11 versions affected across 3 products

Deep dive

Activity timeline180 mentions / 25d
017355269Mentions · 2026-09-07: 3Mentions · 2026-09-08: 69Mentions · 2026-09-09: 40Mentions · 2026-09-10: 11Mentions · 2026-09-11: 12Mentions · 2026-09-12: 2Mentions · 2026-09-13: 2Mentions · 2026-09-14: 4Mentions · 2026-09-15: 3Mentions · 2026-09-16: 4Mentions · 2026-09-17: 4Mentions · 2026-09-18: 1Mentions · 2026-09-19: 2Mentions · 2026-09-21: 3Mentions · 2026-09-22: 2Mentions · 2026-09-24: 2Mentions · 2026-09-26: 1Mentions · 2026-09-27: 1Mentions · 2026-09-30: 3Mentions · 2026-10-01: 2Mentions · 2026-10-08: 3Mentions · 2026-10-15: 1Mentions · 2026-10-16: 1Mentions · 2026-10-17: 3Mentions · 2026-10-19: 1PoC Mentioned / Linked · 2026-09-07: 1PoC Mentioned / Linked · 2026-09-08: 10PoC Mentioned / Linked · 2026-09-09: 2PoC Mentioned / Linked · 2026-09-10: 2PoC Mentioned / Linked · 2026-09-11: 2PoC Mentioned / Linked · 2026-09-12: 1PoC Mentioned / Linked · 2026-09-15: 1PoC Mentioned / Linked · 2026-09-16: 1PoC Mentioned / Linked · 2026-09-17: 2PoC Mentioned / Linked · 2026-09-22: 1PoC Mentioned / Linked · 2026-09-26: 1Exploit Tool / Code · 2026-09-08: 4Exploit Tool / Code · 2026-09-09: 1Exploit Tool / Code · 2026-09-10: 1Exploit Tool / Code · 2026-09-12: 1Exploit Tool / Code · 2026-09-15: 1Exploit Tool / Code · 2026-09-16: 1Exploit Tool / Code · 2026-09-22: 1Active Exploitation · 2026-09-07: 3Active Exploitation · 2026-09-08: 51Active Exploitation · 2026-09-09: 24Active Exploitation · 2026-09-10: 11Active Exploitation · 2026-09-11: 9Active Exploitation · 2026-09-13: 2Active Exploitation · 2026-09-14: 4Active Exploitation · 2026-09-15: 1Active Exploitation · 2026-09-16: 3Active Exploitation · 2026-09-18: 1Active Exploitation · 2026-09-19: 2Active Exploitation · 2026-09-21: 2Active Exploitation · 2026-09-22: 1Active Exploitation · 2026-09-24: 2Active Exploitation · 2026-09-27: 1Active Exploitation · 2026-09-30: 2Active Exploitation · 2026-10-01: 2Patch / Workaround · 2026-09-07: 3Patch / Workaround · 2026-09-08: 46Patch / Workaround · 2026-09-09: 27Patch / Workaround · 2026-09-10: 8Patch / Workaround · 2026-09-11: 8Patch / Workaround · 2026-09-12: 1Patch / Workaround · 2026-09-13: 2Patch / Workaround · 2026-09-15: 1Patch / Workaround · 2026-09-16: 4Patch / Workaround · 2026-09-17: 2Patch / Workaround · 2026-09-19: 1Patch / Workaround · 2026-09-21: 2Patch / Workaround · 2026-09-22: 1Patch / Workaround · 2026-09-24: 2Patch / Workaround · 2026-09-27: 1Patch / Workaround · 2026-10-01: 2Technical Details · 2026-09-07: 2Technical Details · 2026-09-08: 55Technical Details · 2026-09-09: 21Technical Details · 2026-09-10: 11Technical Details · 2026-09-11: 8Technical Details · 2026-09-12: 1Technical Details · 2026-09-13: 2Technical Details · 2026-09-14: 3Technical Details · 2026-09-15: 3Technical Details · 2026-09-16: 4Technical Details · 2026-09-17: 4Technical Details · 2026-09-18: 1Technical Details · 2026-09-19: 2Technical Details · 2026-09-21: 2Technical Details · 2026-09-22: 2Technical Details · 2026-09-24: 2Technical Details · 2026-09-26: 1Technical Details · 2026-09-27: 1Technical Details · 2026-09-30: 1Technical Details · 2026-10-01: 209-0709-0909-1109-1309-1509-1709-1909-2209-2609-3010-0810-1610-19
Signal classification6 categories
Active Exploitation
9756.7%
Patch
4224.6%
General
137.6%
Disclosure
105.8%
PoC
74.1%
Exploit
21.2%
Referenced assets162 URLs
By indicator
Classification over time
DateTotalLabels
2026-09-073
Active Exploitation2Patch1
2026-09-0869
Active Exploitation38Disclosure4General5Patch19PoC3
2026-09-0940
Active Exploitation20Disclosure3General6Patch11
2026-09-1011
Active Exploitation8Patch3
2026-09-1112
Active Exploitation7General1Patch4
2026-09-122
Patch1PoC1
2026-09-132
Active Exploitation1General1
2026-09-144
Active Exploitation4
2026-09-153
Active Exploitation1Disclosure1Exploit1
2026-09-164
Active Exploitation3Disclosure1
2026-09-174
Patch2PoC2
2026-09-181
Active Exploitation1
2026-09-192
Active Exploitation2
2026-09-213
Active Exploitation2Patch1
2026-09-222
Active Exploitation1Exploit1
2026-09-242
Active Exploitation2
2026-09-261
PoC1
2026-09-271
Active Exploitation1
2026-09-303
Active Exploitation2Disclosure1
2026-10-012
Active Exploitation2
Full discourse20 posts
  • ThreatWire@ThreatWire_
    Active Exploitation

    🚨 PoC RELEASED: A public exploit for CVE-2026-75650, a CVSS 10.0 unauthenticated RCE affecting Adobe Commerce, is now available. The flaw can allow remote attackers to execute arbitrary code without authentication or user interaction. ⚠️ The vulnerability is already being exploited in the wild, making the public PoC especially significant. 🔴 Adobe has released a fix in APSB26-146. Patch immediately. 🔗 https://github.com/fortbridge/stylesmuggler #Adobe #AdobeCommerce #Magento #CVE #RCE #PoC #CyberSecurity #Infosec

    Post summary

    A public exploit/PoC for CVE-2026-75650 (CVSS 10.0 unauthenticated RCE in Adobe Commerce) is available, the vulnerability is actively exploited in the wild, and Adobe has issued a fix via advisory APSB26-146.

    0170864310.1K
    1.8K followersView on X
  • FOFA@fofabot
    Disclosure

    ⚠️⚠️ CVE-2026-75650 (CVSS 10.0): Unauthenticated RCE ("StyleSmuggler") in Adobe Commerce & Magento Open Source 🔗FOFA Link: https://en.fofa.info/result?qbase64=YXBwPSJNYWdlbnRvIg%3D%3D 🎯81.2K+ Results are found on http://en.fofa.info in the past year. FOFA Query: app="Magento" 🔖Refer: https://helpx.adobe.com/security/products/magento/apsb26-146.html #OSINT #FOFA #CyberSecurity #Vulnerability

    Post summary

    The message announces the newly disclosed unauthenticated RCE (CVE-2026‑75650) in Adobe Commerce and Magento, highlights its severity (CVSS 10.0), links to FOFA results and an Adobe advisory for remediation.

    219060238.2K
    14.8K followersView on X
  • The Hacker News@TheHackersNews
    Patch

    ⚡ Adobe patches a Magento zero-day already exploited to deploy malware. CVE-2026-75650 abuses Magento template processing for unauthenticated code execution. Attacks have delivered a Rust #Linux backdoor and PHP web shell. How the chain works: https://thehackernews.com/2026/09/adobe-patches-magento-zero-day.html

    Post summary

    Adobe released a patch for CVE‑2026‑75650, a Magento template‑processing flaw that has already been used to deliver a Rust Linux backdoor and a PHP web shell.

    626062629.1K
    2.4M followersView on X
  • HKEPC@hkepcmedia

    【10 分滿分 ❌】Adobe 旗下 Magento 與 Adobe Commerce 近日爆出重大資安危機。代號為「BlockStrap」(CVE-2026-103849)的重大漏洞,在 CVSS 評分中獲評最高的 10.0 滿分,遠端攻擊者完全毋須具備任何身份驗證權限,亦不需管理員介入,即可在網店伺服器上執行任意程式碼並全面接管主機。然而,Adobe 官方卻將此修補列為「第 2 級優先」,只建議商戶在 30 日內完成更新,此舉引來資安業界強烈質疑。 https://www.hkepc.com/26996 該漏洞由資安研究員 vozec 發現,主要成因在於 Magento 的電子郵件範本引擎存在架構缺陷。在官方安全性公告 APSB26-153 發布後不到 24 小時內,Sansec 研究團隊便已成功重現出 4 條不同的遠端程式碼執行(RCE)路徑。 Sansec 分析表示,雖然該漏洞的攻擊鏈路徑相對複雜,但在現代自動化與 AI 輔助逆向工具的普及下,有心人士要將更新修補程式反向解析為可用 Exploit(攻擊腳本)的門檻已大幅降低。針對 Adobe 僅給予 30 天寬限期的評級,Sansec 批評該風險評估過於樂觀,強烈呼籲所有電商業者「即刻召回團隊,今天就必須著手修補」,防範伺服器遭黑客植入後門或竊取消費者信用卡交易資料。 值得注意的是,這已是 Magento 電子郵件範本引擎在短短六個星期內出現的第二個 CVSS 10.0 滿分漏洞。上一個漏洞 CVE-2026-75650(代號「StyleSmuggler」)於 9 月初遭到黑客大規模零日攻擊(Zero-day exploit)後,Adobe 才緊急釋出熱修補(Hotfix),美國網路安全暨基礎設施安全局(CISA)隨後亦將其列入「已知被利用弱點目錄」(KEV)。 Sansec 的技術解析顯示,本次的 BlockStrap 本質上正是對 9 月份防護機制的繞過攻擊。Adobe 先前的防禦邏輯是替可信賴的範本指令加入數碼簽章以供驗證,然而攻擊者發現,只要將惡意指令包裹在子範本內,該筆資料依然會被系統連帶簽名,隨後在上層處理時遭到觸發執行,導致整套防禦架構形同虛設。 Sansec 特別提醒,切勿輕信 Adobe 官方所謂「第 2 級優先」及只需 30 天內修補的建議。面對此等 CVSS 10 分的終極嚴重漏洞,9 月發布的 StyleSmuggler 熱修補與本次 10 月發布的 BlockStrap 更新彼此獨立,商戶必須確保兩個安全性更新皆已完成部署,單靠其中一項並無法涵蓋全部威脅,而且必須立即處理,絕不能拖延。

    1414142.7K
    4.0K followersView on X
  • Nicolas Krassas@Dinosn
    PoC

    RCE PoC Lab for StyleSmuggler Magento CVE-2026-75650 https://github.com/dinosn/cve-2026-75650-magento-validation-lab

    Post summary

    A proof‑of‑concept lab with a GitHub link is shared for the StyleSmuggler Magento RCE vulnerability CVE‑2026‑75650.

    07121155.5K
    162.5K followersView on X
  • Dark Web Intelligence@DailyDarkWeb

    🚨 BLOCKSTRAP: UNAUTHENTICATED CODE EXECUTION FLAW PUTS MAGENTO STORES AT RISK BlockStrap puts Magento stores at risk: CVE-2026-103849 enables unauthenticated code execution (CVSS 3.1: 10.0). In research published October 15, Sansec reproduced 4 attack routes; it reports no live attacks observed. Adobe's October patch (APSB26-153, October 13) is available. The separate StyleSmuggler (CVE-2026-75650) hotfix is also required. https://sansec.io/research/blockstrap-magento-rce Advisory: https://www.adobe.com/trust/security/products/commerce/apsb26-153.html #Magento

    0402135.7K
    209.3K followersView on X
  • CERT@certlv
    Active Exploitation

    ‼️ E-komercijas platformās Adobe Commerce un Magento Open Source ir atklāta kritiska ievainojamība CVE-2026-75650, kas jau tiek aktīvi izmantota uzbrukumos. Tā ļauj neautorizētam uzbrucējam izpildīt patvaļīgu kodu ietekmētajā iekārtā. Vairāk: https://cert.lv/lv/2026/09/kritiska-ievainojamiba-adobe-commerce-un-magento-e-komercijas-platformas https://t.co/0TPUlFDLu3

    Post summary

    The post declares that CVE-2026-75650 is a critical arbitrary code execution flaw in Adobe Commerce and Magento Open Source, actively being exploited in the wild, with no patches or PoC details disclosed.

    0701531.3K
    5.7K followersView on X
  • Nicolas Krassas@Dinosn

    CVE-2026-75650: Magento’s StyleSmuggler RCE Explained https://blog.securelayer7.net/cve-2026-75650-stylesmuggler-magento-rce/

    0101264.9K
    162.6K followersView on X
  • dbugs@ptdbugs
    Exploit

    A PoC/exploit has been discovered for vulnerability CVE-2026-75650 PT ID: PT-2026-86916 Vendor: Adobe Product: Adobe Commerce Description: Adobe Commerce is affected by an Improper Neutralization of Special Elements Used in a Template Engine vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction. Scope is changed. References: • https://dbu.gs/vulnerability/PT-2026-86916 • https://github.com/fortbridge/stylesmuggler

    Post summary

    A PoC/exploit for CVE-2026-75650 affecting Adobe Commerce has been discovered, enabling arbitrary code execution via template injection without user interaction; a GitHub PoC repository is referenced, though no active exploitation or patch information is disclosed.

    020821.2K
    3.7K followersView on X
  • Previdian@PrevidianCyber
    Patch

    Magento StyleSmuggler vulnerability has been assigned CVE-2026-75650. Official patches released (APSB26-14). Overnight we started to see some initial probes for the vulnerability in our honeypots, but no exploitation yet. https://t.co/rJaUAY8RDm

    Post summary

    Magento StyleSmuggler CVE-2026-75650 has patches (APSB26-14) released; initial probes seen but no exploitation yet.

    131601.3K
    174 followersView on X
  • Daily CyberSecurity@Daily_CyberSec
    Active Exploitation

    An Adobe Commerce vulnerability, CVE-2026-75650 (CVSS 10), enables unauthenticated arbitrary code execution and is exploited in the wild. Patch now. #AdobeCommerce #Magento #StyleSmuggler #CVE202675650 #RCE #Ecommerce #ExploitedInTheWild #Infosec https://securityonline.info/adobe-commerce-cve-2026-75650-stylesmuggler/ https://t.co/FfTeR8dthQ

    Post summary

    Adobe Commerce is affected by CVE‑2026‑75650, a high‑severity RCE that is actively exploited in the wild, and a vendor patch is now available.

    13061589
    13.0K followersView on X
  • VulnTracker@vuln_tracker
    Active Exploitation

    CVE-2026-75650: a CVSS 10.0 zero-day, exploited in the wild right now. Sansec discovered "StyleSmuggler" — attackers smuggle PHP code through Magento's template system via the styles property, then trigger it through a failed payment email. No authentication needed. Active attacks started September 4th. Adobe shipped an emergency hotfix (APSB26-146) on September 7th. Affected: Adobe Commerce & Magento Open Source 2.4.4–2.4.9, Adobe Commerce B2B 1.3.3–1.5.3 Patch AND rotate every credential your encryption key touched: admin passwords, API tokens, OAuth secrets, payment gateway credentials. Details: http://vulntracker.io/cves/CVE-2026-75650 #Magento #AdobeCommerce #CVE #ZeroDay #VulnTracker

    Post summary

    The post reports that CVE‑2026‑75650, a zero‑day RCE in Adobe Magento exploitable via StyleSmuggler, is being actively used in the wild; Adobe has issued an emergency hotfix and recommends rotating credentials.

    10044506
    816 followersView on X
  • 보안재테크@ngnicky
    Active Exploitation

    인증되지 않은 공격자에게 원격 코드 실행 권한을 부여하는 Magento 및 Adobe Commerce 제로데이 취약점인 StyleSmuggler를 발견 공격은 9월 4일부터 시작. Adobe는 9월 7일에 CVE-2026-75650(CVSS 10.0 등급)에 대한 긴급 핫픽스를 발표. 2.4.4부터 2.4.9까지 영향 https://sansec.io/research/stylesmuggler-0day

    Post summary

    A zero‑day vulnerability (CVE‑2026‑75650) called StyleSmuggler allows remote code execution in Magento/Adobe Commerce, was actively exploited from September 4, and Adobe released an emergency hotfix on September 7.

    01161476
    7.8K followersView on X
  • Teegra 🧝‍♀️𝕏@Teeegra
    Active Exploitation

    شرکت ادوبی روز دوشنبه وصله‌های امنیتی برای رفع یک آسیب‌پذیری بحرانی در Adobe Commerce و Magento Open Source منتشر کرد که هم‌اکنون مورد بهره‌برداری فعال قرار گرفته است. این آسیب‌پذیری با شناسه CVE-2026-75650 (با امتیاز CVSS برابر با ۱۰ از ۱۰، یعنی بالاترین سطح شدت) ردیابی می‌شود و شرکت امنیتی Sansec آن را «StyleSmuggler» نام‌گذاری کرده است. این شرکت از تاریخ ۴ سپتامبر ۲۰۲۶ بهره‌برداری از این نقص را به‌صورت روز-صفر (zero-day) کشف کرد. ادوبی اعلام کرد: «این به‌روزرسانی یک آسیب‌پذیری بحرانی را برطرف می‌کند که می‌تواند منجر به اجرای کد دلخواه (arbitrary code execution) شود» و افزود که «از بهره‌برداری در دنیای واقعی از CVE-2026-75650 علیه فروشندگان Adobe Commerce آگاه است». در هسته این آسیب‌پذیری، مهاجم با سوءاستفاده از سامانه قالب (template) مجنتو از طریق تزریق کد PHP، یک ایمیل با عنوان «یادآوری ناموفق بودن تراکنش پرداخت» تولید می‌کند که در این فرآیند منجر به اجرای کد می‌شود. این نقص نسخه‌های متعددی از Adobe Commerce، Adobe Commerce B2B و Magento Open Source را تحت تأثیر قرار می‌دهد. ادوبی توصیه کرده کاربران علاوه بر اعمال وصله VULN-39341، کلیدهای رمزنگاری (encryption keys) خود را نیز تغییر دهند.

    Post summary

    CVE‑2026‑75650, a zero‑day with CVSS 10/10, is actively exploited in the wild; Adobe has issued patch VULN‑39341 and advises users to rotate encryption keys.

    00080740
    20.3K followersView on X
  • YourDailyCVE@YourDailyCVE
    Active Exploitation

    🚨 CVE-2026-75650 — StyleSmuggler. Magento / Adobe Commerce, unauth RCE. CVSS 10.0. What broke: Magento’s template engine can be tricked into running attacker code. No login. No click. Attackers used that to plant backdoors on live stores starting 4 Sep, three days before Adobe shipped a fix. Who should care: anyone running an online store on Adobe Commerce or Magento Open Source 2.4.4–2.4.9, including the August 2026 builds. B2B 1.3.3–1.5.3 too. July and August security patches do not cover this. Sansec reproduced it on clean 2.4.7, 2.4.8, and 2.4.9. Why that matters: This is unauthenticated remote code execution on your e-commerce server — full compromise of the store, its data, and its hosting environment. Attackers are already using it to install a persistent Linux backdoor and, separately, a PHP web shell for hands-on remote control. For a store, that typically means exposure of customer data and payment information, plus the store itself potentially being turned into a launchpad for further attacks. Status: exploited from 4 Sep. Adobe confirmed it in APSB26-146 (7 Sep). Priority 1. Not on CISA KEV yet. Fix today: apply hotfix VULN-39341 (APSB26-146). Then rotate encryption keys and every secret on that host — admin passwords, GraphQL tokens, OAuth, payment-gateway keys, DB creds, SSH, API keys. Flush cache after. Can't patch tonight: take GraphQL / the store admin off the raw internet if you can. Hunt for odd “Payment Transaction Failed Reminder” mail and unexpected processes. Still apply the hotfix; isolation is not a substitute. Do this now: if you run Magento or Adobe Commerce, apply VULN-39341 today, rotate keys, and reply “patched.” Source: Adobe APSB26-146 / Sansec / BleepingComputer #Magento #AdobeCommerce

    Post summary

    CVE-2026-75650 is actively being exploited in Magento/Adobe Commerce stores via unauthenticated RCE; Adobe released a hotfix (VULN-39341) and recommends immediate application and key rotation to mitigate persistent backdoor threats.

    21041255
    36 followersView on X
  • Jonatas ➔ 🐕 caramelosec.com@kyoto01z
    Active Exploitation

    O código do atacante não roda na hora do ataque. Ele roda depois, sozinho, quando a loja monta um e-mail automático de pagamento recusado. Esse é o CVE-2026-75650, o StyleSmuggler. Pega Magento e Adobe Commerce, nota 10.0, sem precisar de login. O Magento tem um sistema de template com diretivas próprias, e travas pra impedir que PHP entre por ali. O truque foi mandar a carga pela propriedade styles, que passa por fora dessas travas. É daí que vem o nome. A primeira fase só escreve. O atacante provoca um relatório de falha, e o PHP dele fica guardado. A segunda fase acontece quando a loja renderiza o lembrete de transação recusada. Renderizar o template executa o que tem dentro. Ninguém precisa abrir esse e-mail. A execução é no servidor, enquanto a mensagem está sendo montada. Repare no que isso faz com a investigação. A hora do ataque e a hora da execução são momentos diferentes. O que instalaram foi um programa em Rust que fica esperando comando do atacante. Ele se disfarça com nome de processo do sistema, tipo chronyd. Afeta da 2.4.4 até a 2.4.9. A exploração começou dia 4, a Sansec divulgou dia 5, e o hotfix da Adobe saiu dia 7. São três dias de loja invadida com tudo atualizado. Aqui em casa a gente cuida do básico do seu site: http://caramelosec.com 🐕 #bolhasec #bolhadev

    Post summary

    The note reports that CVE‑2026‑75650 was actively exploited in Magento/Adobe Commerce via a Rust program that hijacks style templates in auto‑generated emails; attacks ran for three days before a hotfix was issued.

    12040234
    204 followersView on X
  • DFIR Radar@DFIR_Radar
    Active Exploitation

    CVE-2026-75650, CVSS 10.0 zero-day in Adobe Commerce and Magento Open Source, is actively exploited. Unauthenticated RCE via template injection deployed Rust backdoors and PHP web shells before Adobe's Sept 7 patch. Key findings: - StyleSmuggler (CWE-1336) poisons a server-accessible file (app log or var/report/) with attacker PHP, then triggers Magento's template engine through the Payment Transaction Failed Reminder email flow to include and execute it. No account, no user interaction required. Full August 2026 security updates offered zero protection. - Two distinct post-exploitation paths confirmed: a Rust-based Linux implant masquerading as [kworker/u:8:0], fc-cache, or chronyd, persisting via cron and UDP/123 NTP-like traffic; and a PHP web shell dropped under pub/media/catalog/product/cache/ returning 404 until triggered with X-Cache-Token header. C2 infrastructure resolved to 185.157.160[.]251. - First exploitation confirmed Sept 4 at 22:20 UTC, three days before Adobe bulletin APSB26-146 and hotfix VULN-39341 shipped. Any internet-facing store in that window must be treated as potentially compromised, not just unpatched. - Malware survived file deletion by relocating outside the webroot, re-establishing cron persistence, and continuing execution. Deleting the web shell is not remediation. Apply VULN-39341 and rotate Commerce encryption keys now. #DFIR_Radar

    Post summary

    The post confirms CVE-2026-75650 is actively exploited via template injection, with detailed attack stages and Rust/PHP payloads, and urges immediate patching and key rotation.

    20032327
    2.0K followersView on X
  • DFIR Radar@DFIR_Radar

    CVE-2026-88771, a CVSS 9.8 unauthenticated RCE in Citrix NetScaler ADC and Gateway, is actively exploited in the wild and listed in CISA KEV. Patch immediately, but preserve forensics first. - CVE-2026-88771 requires no authentication and no optional features. The attack works by poisoning the HTTP access log with Base64-encoded shell commands in a User-Agent value beginning "INDEX:", then submitting a forged pitboss PPE failure string to /nf/auth/doAuthentication.do or /cgi/login. The legitimate NetScaler Perl script /netscaler/ns_monuploadd_err.pl later processes PPE failure records from /var/log/ns.log, selects the last matching line, and passes attacker-controlled content to a shell without escaping metacharacters. That is the trigger: no direct exploit request fires the code, a trusted diagnostic script does it. - Once execution lands, the payload creates directories, writes fingerprint HTML files using the prefix Nx_ (observed as Nx_7508.html and Nx_5936.html) across /var/vpn/bookmark/, /netscaler/ns_gui/vpn/, /var/netscaler/gui/vpn/, /var/vpn/theme/, and /var/netscaler/logon/LogonPoint/, then drops PHP and Perl web shells with the same naming pattern. It also modifies /etc/httpd.conf to flip php_engine off to php_engine on and appends AddHandler cgi-script .pl, then sends Apache a HUP signal. An inline variant fetched a Rust-based FreeBSD x64 binary named kw2-freebsd-x64-s11 from 209.141.43[.]95 to /var/kw2s11 and executed it. - ThreatLabz observed a coordinated burst from at least 26 source IP addresses over roughly six to seven minutes, all following the same log-poisoning and FreeBSD payload-delivery sequence. The download server at 209.141.43[.]95 also appeared in exploitation of CVE-2026-75650 (StyleSmuggler, CVSS 10.0, Adobe Commerce and Magento). Shared infrastructure across two unrelated platforms suggests a common operator or malware-distribution service, though attribution is not confirmed. The full IOC table with 27 source IPs is in the report. - CISA warns that patching before evidence collection can destroy forensic visibility. Before upgrading, capture a VM snapshot where possible, collect the NetScaler technical support bundle, remote syslog data, and packet-engine core dumps. Then search HTTP access logs for User-Agent values starting with "INDEX:" followed by Base64 content. Search /var/log/ns.log and /var/log/messages for forged pitboss PPE strings containing shell syntax. Find newly written files in webroot paths with: find /netscaler/ns_gui/ /var/netscaler/gui/ /var/vpn/ -type f -mtime -3. Look for Nx_*.php and Nx_*.pl alongside unexpected Nx_*.html fingerprint files. Check /etc/httpd.conf for php_engine on and AddHandler cgi-script .pl modifications. Run ps aux and grep for shells spawned under the nobody service context, and netstat -an to surface unexpected listening ports. Practitioner takeaway: Hunt for the INDEX: User-Agent pattern in HTTP access logs and forged pitboss PPE strings in ns.log before you touch the upgrade. Those two log sources together reconstruct the full pre-execution chain. Fixed builds are NetScaler ADC and Gateway 14.1-73.46 and 13.1-64.29. Rotate all credentials, tokens, and certificates stored on or reachable through any appliance confirmed compromised. #DFIR_Radar

    11031357
    2.0K followersView on X
  • DFIR Radar@DFIR_Radar

    Chinese 🇨🇳 AI-assisted penetration testing framework ARTEX has fragmented into multiple rebranded forks after its GitHub repo went dark, with at least one operator deploying it alongside a live CVE-2026-75650 Magento RCE exploit and an IRC-based PHP implant. Key findings: - ARTEX has spawned at least six confirmed rebrands: ScopeWeaver, Tangora PTaaS, Horda, Meze, AegisLoop, and Bob Research Labs / THE GRIM REAPER. The core multi-agent orchestration architecture, PostgreSQL-backed task state, and Planner-plus-three-Workers model carry across all of them, making the shared lineage traceable even when product names and UIs are replaced. Hunt for the reaper-full project name and artex-linux-amd64 references in exposed internal paths. - The Bob Research Labs / REAPER instance exposed two frontends on TCP ports 3001 and 443, ran LLM profiles backed by DeepSeek, GLM, Kimi, and Claude, and carried a bobresearch agent profile. The multi-LLM backend design means operators can swap inference providers without restructuring the attack pipeline, a capability gap that commodity red-team tooling does not yet reflect. - CVE-2026-75650, an unauthenticated remote code execution flaw in Magento/Adobe Commerce, was actively staged in the Bob Research Labs environment using StyleSmuggler, the public PoC. Evidence of execution steps was present: Guest Cart creation, billing information manipulation, triggering the vulnerable checkout flow, and extraction of the Magento Report Identifier. The follow-up dropped cache.php and testnewbot.php, and an "IRC BOT DEPLOYED" message was logged. - irc.php functions as a persistence-anchored IRC C2 implant. It connects to the password-protected channel mg_master, installs itself via an [@]reboot cron job, copies itself to hidden paths, supports multiple PHP execution functions, and accepts !Cmd@ and !Cmd@all commands for remote tasking. This is post-exploitation infrastructure, not a scanner artifact. - Korean localization artifacts are widespread across forks: Korean strings embedded in Go code handling SMTP, Notes, and HTTP processing; a translate_go.py script mapping Korean and Chinese 🇨🇳 strings to English; and an artex-ko directory. Skills packages (skills-en-keep, skills-backup, skills-translated-en[.]zip, bob-research-skills-en[.]zip) show a deliberate workflow of collecting, translating, and repackaging attack playbooks covering SQL injection, SSRF, XSS, XXE, IDOR, command injection, cloud and container testing, and more. Practitioner takeaway: If you work Magento incident response, look for cache.php, testnewbot.php, and irc.php in the webroot and cache directories. Check crontabs for [@]reboot entries pointing to PHP processes and outbound IRC connections from the web tier. For threat hunters tracking ARTEX-lineage infrastructure, exposed PostgreSQL instances with task-state tables, dual-port frontends (3001/443), and artex-linux-amd64 binary references in process or path artifacts are the fingerprint. The AhnLab ASEC report documents IOCs, credential exposures, and runtime artifacts found in the wild. #DFIR_Radar

    21021431
    2.0K followersView on X
  • FORTBRIDGE@FORTBRIDGE
    PoC

    We reproduced the full unauthenticated Magento StyleSmuggler chain (CVE-2026-75650) over HTTP, from report poisoning and template directive smuggling to the final PHP include. Technical analysis and PoC: https://fortbridge.co.uk/research/stylesmuggler-magento-unauthenticated-rce/ #Magento #CyberSecurity

    Post summary

    The post details the reproduction of the unauthenticated Magento StyleSmuggler chain and provides a link to a PoC, offering technical insight but no active exploitation or patch information.

    02040273
    179 followersView on X
CPE platform detail185 entries

185 of 185 entries

PartVendorProductVersionTarget SWTarget HW
Appadobecommerce---
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.4--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.5--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.6--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.7--
Appadobecommerce2.4.8--
Appadobecommerce2.4.8--
Appadobecommerce2.4.8--
Appadobecommerce2.4.8--
Appadobecommerce2.4.8--
Appadobecommerce2.4.8--
Appadobecommerce2.4.8--
Appadobecommerce2.4.8--
Appadobecommerce2.4.9--
Appadobecommerce2.4.9--
Appadobecommerce2.4.9--
Appadobecommerce2.4.9--
Appadobecommerce2.4.9--
Appadobecommerce_b2b---
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.3--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.3.4--
Appadobecommerce_b2b1.4.2--
Appadobecommerce_b2b1.4.2--
Appadobecommerce_b2b1.4.2--
Appadobecommerce_b2b1.4.2--
Appadobecommerce_b2b1.4.2--
Appadobecommerce_b2b1.4.2--
Appadobecommerce_b2b1.4.2--
Appadobecommerce_b2b1.4.2--
Appadobecommerce_b2b1.4.2--
Appadobecommerce_b2b1.4.2--
Appadobecommerce_b2b1.4.2--
Appadobecommerce_b2b1.5.2--
Appadobecommerce_b2b1.5.2--
Appadobecommerce_b2b1.5.2--
Appadobecommerce_b2b1.5.2--
Appadobecommerce_b2b1.5.2--
Appadobecommerce_b2b1.5.2--
Appadobecommerce_b2b1.5.3--
Appadobecommerce_b2b1.5.3--
Appadobecommerce_b2b1.5.3--
Appadobecommerce_b2b1.5.3--
Appadobecommerce_b2b1.5.3--
Appadobemagento---
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.6--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.7--
Appadobemagento2.4.8--
Appadobemagento2.4.8--
Appadobemagento2.4.8--
Appadobemagento2.4.8--
Appadobemagento2.4.8--
Appadobemagento2.4.8--
Appadobemagento2.4.8--
Appadobemagento2.4.8--
Appadobemagento2.4.9--
Appadobemagento2.4.9--
Appadobemagento2.4.9--
Appadobemagento2.4.9--
Appadobemagento2.4.9--

Explore more