# CVE-2026-71362: Adobe Commerce and Magento Incorrect Authorization Vulnerability

> An attacker can gain elevated access to sensitive resources in Adobe Commerce without user interaction due to incorrect authorization checks.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Yes, since 24 Sep 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-f58v-hxr9-8947, ROOT-APP-COMPOSER-CVE-2026-71362

## What is CVE-2026-71362?

CVE-2026-71362 is a critical missing authorization vulnerability in Adobe Commerce, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Adobe Commerce is affected by an Incorrect Authorization vulnerability that could result in privilege escalation. An attacker could leverage this vulnerability to gain elevated access to sensitive resources. Exploitation of this issue does not require user interaction.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-71362?

It affects 3 products.


Products: Adobe Commerce, Adobe Commerce B2b, Adobe Magento.

## How do I fix CVE-2026-71362?

Apply the vendor's patch. US federal agencies must fix it by 27 Sep 2026.

## Is CVE-2026-71362 being exploited?

Yes. Attackers have exploited CVE-2026-71362 in the wild since at least 24 Sep 2026.

Public exploit code:

- One-command Docker lab reproducing CVE-2026-71362 (Adobe Commerce / Magento Open Source customer-session identity-switch account takeover, APSB26-92, CVSS 9.1) with a PoC and an A/B/A official-patch negative control. For authorized security research and education. (github_poc): https://github.com/dinosn/cve-2026-71362-magento-lab
- CVE-2026-71362 — Magento Session Identity Poisoning → Mass Account Takeover (CVSS 9.1, CISA KEV) (github_poc): https://github.com/mahumadad/cve-2026-71362-magento-ato
- Adobe Commerce/Magento - Customer Session Identity Switch (nuclei): http/cves/2026/CVE-2026-71362.yaml

## Other vulnerabilities in Adobe Commerce

- [CVE-2026-75650](https://insights.sbomify.com/CVE-2026-75650/): Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine (critical 10.0, exploited in the wild)
- [CVE-2024-34102](https://insights.sbomify.com/CVE-2024-34102/): Adobe Commerce and Magento Open Source Improper Restriction of XML External Entity Reference (XXE) (critical 9.8, exploited in the wild)
- [CVE-2022-24086](https://insights.sbomify.com/CVE-2022-24086/): Adobe Commerce and Magento Open Source Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2026-48356](https://insights.sbomify.com/CVE-2026-48356/): Adobe Commerce and Magento Unrestricted Upload of File with Dangerous Type (critical 9.3, exploited in the wild)
- [CVE-2025-54236](https://insights.sbomify.com/CVE-2025-54236/): Adobe Commerce and Magento Improper Input Validation (critical 9.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71362 and fix it if it is affected.

What it is: CVE-2026-71362 is a critical missing authorization vulnerability in Adobe Commerce, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-71362 in the wild since at least 24 Sep 2026.

Affected product: Adobe Commerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71362/ (Markdown: https://insights.sbomify.com/CVE-2026-71362/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71362
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71362
- OSV: https://osv.dev/vulnerability/CVE-2026-71362

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71362/
Summaries are generated and may contain mistakes; the official description above is the record.