Advisory

CVE-2026-71362: Critical Adobe Commerce & Magento Incorrect Authorization Flaw (CVSS 9.1)

Adobe Commerce and Magento contain a critical incorrect authorization vulnerability (CVE-2026-71362) that allows unauthenticated, remote attackers to escalate privileges and gain elevated access to sensitive resources without any user interaction. The flaw carries a CVSS 3.1 score of 9.1 and has been added to the CISA Known Exploited Vulnerabilities catalog.

TL;DR: Apply Adobe's vendor-issued mitigations immediately in line with CISA BOD 26-04 requirements; if patches are unavailable, consider discontinuing internet-facing use of the affected product. Federal agencies and critical infrastructure operators should treat this as a priority remediation.

What Is CVE-2026-71362?

CVE-2026-71362 is an Incorrect Authorization vulnerability (classified under CWE-863) affecting Adobe Commerce and Magento. The flaw was published to the National Vulnerability Database on 11 August 2026 and was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 24 September 2026.

Incorrect Authorization flaws arise when an application does not properly enforce access controls, allowing an actor to perform operations or access resources beyond their intended permission level. In this case, the vulnerability can be exploited to achieve privilege escalation, granting an attacker elevated access to sensitive resources within the Commerce or Magento platform.

Key technical attributes from the NVD record include:

  • CVSS 3.1 Score: 9.1 — Critical
  • Attack Vector: Network (remote exploitation possible)
  • Attack Complexity: Low (no special conditions required)
  • Privileges Required: None (no account needed to exploit)
  • User Interaction: None (fully weaponizable without victim participation)
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: None

The combination of network accessibility, low complexity, and zero required privileges or user interaction makes this an exceptionally dangerous flaw for any internet-facing Adobe Commerce or Magento deployment.

Who and What Is Affected?

The vulnerability affects Adobe Commerce and Magento. The NVD advisory and CISA KEV entry do not enumerate specific version ranges within the provided facts; consult Adobe's official vendor advisory directly to confirm whether your installed version falls within the affected range.

Organizations most at risk include:

  • E-commerce merchants running self-hosted or cloud-managed Adobe Commerce or Magento storefronts.
  • Hosting providers and managed service partners operating Commerce or Magento on behalf of clients.
  • Federal agencies subject to CISA Binding Operational Directive (BOD) 26-04, for whom remediation of KEV entries carries mandatory timelines.
  • Any organization with an internet-exposed Commerce or Magento administration panel or API endpoint, given the network-based, no-authentication-required attack vector.

Because exploitation requires no account credentials and no user interaction, the attack surface extends to any network path that can reach the vulnerable application — including through content delivery networks, reverse proxies, or cloud load balancers that may otherwise obscure the backend technology stack from casual observation.

Understanding the Impact

According to the NVD description and CISA KEV summary, successful exploitation of CVE-2026-71362 enables an attacker to gain elevated access to sensitive resources within the Adobe Commerce or Magento environment. The CVSS vector confirms high impact to both confidentiality and integrity, with no availability impact recorded.

In practical terms for a Commerce or Magento platform, privileged access can translate to:

  • Unauthorized access to customer data, including order history, personally identifiable information, and stored payment references managed by the platform.
  • Manipulation of product catalog data, pricing, or discount rules, undermining the integrity of the storefront.
  • Creation or modification of administrative accounts, enabling persistent access that survives initial incident response.
  • Potential access to integration credentials (payment gateways, ERP connectors, shipping APIs) stored within the platform configuration.

CISA's inclusion of this CVE in the KEV catalog on 24 September 2026 indicates that exploitation has been observed in real-world environments. Organizations should treat the threat as active rather than theoretical.

Note: The scope of exploitation observed in the wild is characterised by CISA's KEV listing; specific incident details are not disclosed in the available facts and are not stated here.

What to Do Now

CISA's required action for CVE-2026-71362 is clear: apply mitigations in accordance with vendor instructions, ensuring compliance with BOD 26-04 patching guidelines and CISA's Forensics Triage Requirements. If mitigations are unavailable, CISA directs organizations to discontinue use of the product in internet-facing configurations. The following steps reflect that guidance:

  1. Consult Adobe's official advisory. Obtain patch or mitigation details directly from Adobe for Commerce and Magento. Do not rely on third-party summaries alone for version-specific patch information.
  2. Prioritize internet-facing instances. Systems directly reachable from the public internet carry the highest risk given the network-based, unauthenticated attack vector. Prioritize these for immediate patching.
  3. Apply BOD 26-04 timelines. Federal agencies must comply with the patching deadlines prescribed in CISA's Binding Operational Directive 26-04. Review the directive (available at CISA's website) for asset classification and deadline requirements.
  4. Conduct forensic triage. Per CISA's Forensics Triage Requirements referenced in the KEV entry, assess whether systems may already be compromised before applying patches. Patching a compromised host without triage may preserve attacker persistence.
  5. Review access logs and admin accounts. Look for anomalous privilege escalation events, unexpected administrative account creation, or unusual API activity in the period following the vulnerability's publication date of 11 August 2026.
  6. Restrict administrative access. While patching is underway, consider IP allowlisting or VPN-gating Commerce and Magento administration interfaces where operationally feasible.
  7. Notify downstream stakeholders. If you operate Commerce or Magento on behalf of clients, inform them of the vulnerability, your remediation timeline, and any forensic findings per your contractual and regulatory obligations.

How Continuous External Testing Surfaces This Exposure

CVE-2026-71362 exemplifies why point-in-time penetration tests are insufficient for modern e-commerce security programs. The flaw was published in August 2026, added to CISA KEV in September 2026, and organizations without continuous external visibility may have remained exposed for weeks or longer without awareness.

Continuous external attack surface monitoring and testing provides several defensive advantages relevant to this vulnerability:

  • Fingerprinting of exposed Commerce/Magento instances. External scanning can identify internet-facing deployments of Adobe Commerce and Magento across your known and unknown asset inventory, including shadow IT storefronts or staging environments inadvertently left public.
  • Rapid detection of newly disclosed CVEs against live assets. When a critical CVE like CVE-2026-71362 is published, continuous testing platforms can immediately cross-reference your external attack surface against the affected product set, reducing the time-to-awareness from weeks to hours.
  • Validation that patches are correctly applied. After vendor mitigations are deployed, external testing confirms that the fix is in effect from an attacker's vantage point — not merely that an internal change management ticket is closed.
  • Misconfiguration detection. Authorization flaws classified under CWE-863 often coexist with broader access control misconfigurations. Continuous external testing surfaces unexpected administrative interfaces, unauthenticated API endpoints, and over-permissive configurations before attackers find them.
  • BOD 26-04 compliance evidence. Continuous testing generates the external-perspective evidence needed to demonstrate timely remediation to auditors and regulators.

Organizations relying solely on internal vulnerability scanners will miss the attacker's true external view — particularly relevant for CVE-2026-71362, where the attack vector is fully network-based and unauthenticated.

Sources & further reading: NVD CVE-2026-71362 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: helpx.adobe.com, cisa.gov. This advisory contains no exploit code.

Frequently asked questions

Is CVE-2026-71362 being actively exploited?

Yes. CISA added CVE-2026-71362 to its Known Exploited Vulnerabilities (KEV) catalog on 24 September 2026, indicating that exploitation has been observed in real-world environments. Organizations should treat the threat as active and prioritize remediation accordingly.

Do attackers need an account or any user interaction to exploit this flaw?

No. According to the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N), the vulnerability is exploitable over the network with low attack complexity and requires neither prior credentials nor any action from a victim user. This makes it particularly dangerous for internet-facing deployments.

What specific versions of Adobe Commerce and Magento are affected?

The verified facts do not enumerate specific version ranges. You should consult Adobe's official vendor advisory directly to determine whether your installed version is affected and to obtain the correct patch or mitigation instructions.

What must U.S. federal agencies do about this vulnerability?

CISA's required action directs all organizations — and especially federal agencies subject to BOD 26-04 — to apply vendor-provided mitigations in accordance with BOD 26-04 patching timelines and CISA's Forensics Triage Requirements. If no mitigations are available, agencies should discontinue internet-facing use of the product. Refer to CISA's official BOD 26-04 and KEV catalog pages for mandatory deadlines.