Adobe Commerce and Magento: attackers can run their own code
OFFICIAL NAME: Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine Vulnerability
WHAT IT IS · WEBSITE OR ONLINE STOREIt runs public websites, online stores or the software behind them.
DO THIS FIRSTAsk whoever runs your website or store to update it. Not sure if you use it? Send this page to your IT provider or security lead and ask.
TECHNICAL SUMMARY Adobe Commerce and Magento Open Source contain an improper neutralization of special elements used in a template engine vulnerability that could allow an attacker to execute arbitrary code.
WHY THIS VERDICT Attacks are confirmed. The vulnerability is 61 days old, so current versions are being attacked. Ready-made attack tools are public. The severity score is critical (10.0). The exploit prediction score is 99%.
- HIGHEST CONFIRMED RUNG
- EXPLOITED
- CISA KEV
- LISTED
- EXPLOIT CODE
- READY TO USE
How far has it climbed?
01 TALK
▨ REPORTED, NOT CONFIRMEDNEWEST EVIDENCE · 1 SOURCECVE-2026-75650 discussed publicly (CIRCL sighting). CVE-2026-75650 discussed publicly (CIRCL sighting).
02 EXPOSED
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETWe have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.
03 TRIED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESAttacks that worked are confirmed (step 4), so attempts count as confirmed too.
04 EXPLOITED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESAdobe Commerce and Magento Open Source contain an improper neutralization of special elements used in a template engine vulnerability that could allow an attacker to execute arbitrary code. CISA Vulnrichment marks CVE-2026-75650 as actively exploited.
05 DAMAGE
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETBreach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.
When each thing happened
- DISCLOSED
- EXPLOIT CODE PUBLIC
- FIRST ATTACK REPORT
- CISA KEV LISTING
- US FEDERAL DEADLINE
THE FIX
CISA's instruction: apply the vendor's fix, or stop using the product if no fix exists. The deadline CISA set for US federal agencies, Sep 11, 2026, has passed. It is a US government deadline; use it as a guide.
Questions to ask this week
- Do we run Adobe Commerce and Magento? If yes, is it patched or cut off from the internet?
- Who owns fixing it, and by what date?
- Have we checked for signs of attack since the first report, not just since the patch?
How it unfolded
- SEP 7, 20266 public GitHub repositories claim a proof of concept for CVE-2026-75650
- Attack activity. SEP 7, 2026CISA Vulnrichment marks CVE-2026-75650 as actively exploited
- Attack activity. SEP 7, 2026Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine Vulnerability
- OCT 25, 2026Public proof of concept for CVE-2026-75650 (CIRCL sighting)
- NOV 2, 2026CVE-2026-75650 discussed publicly (CIRCL sighting) (3 reports, latest NOV 5)
SOURCES
- [1] nuclei-templates: Nuclei scan template: Adobe Commerce/Magento <= 2.4.9 - StyleSmuggler Unauthenticated RCE via SSTI, NOV 3
- [2] CIRCL Vulnerability-Lookup sightings: CVE-2026-75650 discussed publicly (CIRCL sighting), NOV 5
- [3] CIRCL Vulnerability-Lookup sightings: Public proof of concept for CVE-2026-75650 (CIRCL sighting), OCT 25
- [4] CISA Known Exploited Vulnerabilities: Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine Vulnerability, SEP 7
- [5] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment marks CVE-2026-75650 as actively exploited, SEP 7
- [6] PoC-in-GitHub: 6 public GitHub repositories claim a proof of concept for CVE-2026-75650, SEP 7
- [7] CIRCL Vulnerability-Lookup sightings: 2 more reports