Adobe Commerce and Magento: attackers can gain admin rights
OFFICIAL NAME: Adobe Commerce and Magento Incorrect Authorization 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 contains an incorrect authorization vulnerability that could allow an attacker to leverage this vulnerability to gain elevated access to sensitive resources without any user interaction.
WHY THIS VERDICT Attacks are confirmed. The vulnerability is 91 days old, so many systems are likely still unpatched. Ready-made attack tools are public. The severity score is critical (9.1). The exploit prediction score is 92%.
WHY IT RANKS HERE Exploitation is confirmed by an authoritative source. Ready-made attack tools are public. 4 products are affected.
- 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-71362 discussed publicly (CIRCL sighting). CVE-2026-71362 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 contains an incorrect authorization vulnerability that could allow an attacker to leverage this vulnerability to gain elevated access to sensitive resources without any user interaction. CISA Vulnrichment marks CVE-2026-71362 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 27, 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
- Attack activity. AUG 11, 2026CISA Vulnrichment marks CVE-2026-71362 as actively exploited
- AUG 15, 20262 public GitHub repositories claim a proof of concept for CVE-2026-71362
- AUG 17, 2026Vulnerability CVE-2026-71362 confirmed by a researcher (CIRCL sighting)
- Attack activity. SEP 23, 2026Adobe Commerce and Magento Incorrect Authorization Vulnerability
- OCT 24, 2026CVE-2026-71362 discussed publicly (CIRCL sighting) (4 reports)
SOURCES
- [1] nuclei-templates: Nuclei scan template: Adobe Commerce/Magento - Customer Session Identity Switch, OCT 24
- [2] CIRCL Vulnerability-Lookup sightings: CVE-2026-71362 discussed publicly (CIRCL sighting), OCT 24
- [3] CISA Known Exploited Vulnerabilities: Adobe Commerce and Magento Incorrect Authorization Vulnerability , SEP 23
- [4] CIRCL Vulnerability-Lookup sightings: Vulnerability CVE-2026-71362 confirmed by a researcher (CIRCL sighting), AUG 17
- [5] PoC-in-GitHub: 2 public GitHub repositories claim a proof of concept for CVE-2026-71362, AUG 15
- [6] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment marks CVE-2026-71362 as actively exploited, AUG 11
- [7] CIRCL Vulnerability-Lookup sightings: 3 more reports