CVE-2026-71362: Adobe Commerce / Magento incorrect authorization, privilege escalation

Exploited in the wild Critical 9.1 EPSS 90.5% Magento / Adobe Commerce

An incorrect authorization flaw in Adobe Commerce and Magento Open Source lets an unauthenticated attacker gain elevated access to sensitive resources (critical, CVSS 9.1). It was fixed in the August 11, 2026 security update APSB26-92. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-09-24.

What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms

What to do now

  1. Check whether you run Magento / Adobe Commerce and which version (commands below).
  2. Install the fixed version for your system: see “Patch it” below.
  3. Flush the Magento cache after patching. On Adobe Commerce on Cloud, commit the patch files into m2-hotfixes/ and redeploy (the fix is also in the latest Magento Cloud Patches).
  4. Because this flaw is being exploited, also check the server for signs of compromise.

Affected and fixed versions

Affected:

Fixed in:

Am I affected?

php bin/magento --version
php vendor/bin/patch-status

Patch it

Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.

Debian
not packaged: composer require magento/product-community-edition
Ubuntu
not packaged: composer
RHEL, AlmaLinux, Rocky, Oracle
not packaged: composer
Fedora
not packaged
SUSE / openSUSE
not packaged
Amazon Linux
not packaged: composer
Arch Linux
not packaged
Alpine
not packaged
FreeBSD
not packaged
Built from source
# Adobe ships the August 2026 fix as Isolated patch files (no Composer packages).
# Isolated patches are cumulative-in-order: the matching July 2026 patch must already be applied.
# 1. Be on the latest -p release of your line (2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15, 2.4.5-p17, 2.4.4-p18).
# 2. Download the matching 2-4-x-...-aug-2026.zip from Adobe KB ka-40380 and unzip it in the Magento root.
# 3. Apply July then August files, CE before EE before B2B, e.g. for 2.4.6-p15 EE:
cd /path/to/magento
patch -p1 < 246p15-2026-07-001-CE.patch
patch -p1 < 246p15-2026-07-001-EE.patch
patch -p1 < 246p15-2026-08-001-CE.patch
patch -p1 < 246p15-2026-08-001-EE.patch
php bin/magento cache:flush
php vendor/bin/patch-status

General update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.

CISA required action: 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.

https://helpx.adobe.com/security/products/magento/apsb26-92.html ; ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-71362

Related vulnerabilities

Sources

Page generated automatically from official sources on 2026-11-03 18:05 UTC and reviewed by an editor. Always confirm with your vendor's advisory.