Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-71362 – Privilege Escalation via Incorrect Authorization – Adobe Commerce, Adobe Commerce B

Be the first to know when new zero-days emerge:

Summary

CVE-2026-71362 is an Incorrect Authorization vulnerability (CWE-863) affecting Adobe Commerce, Adobe Commerce B2B, and Magento Open Source. The flaw allows an unauthenticated, remote attacker to escalate privileges and obtain elevated access to the application without any user interaction. Adobe rates this issue Critical with a CVSS v3.1 base score of 9.1.

Technical details

  • Root cause: The application fails to correctly enforce authorization checks (CWE-863: Incorrect Authorization), allowing access-control decisions to be bypassed.
  • Trigger conditions: No authentication or user interaction is required; the flaw can be triggered by a remote, unauthenticated attacker sending requests over the network.
  • Attack vector: Network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
  • Impact: High confidentiality and integrity impact (privilege escalation and elevated access to protected data/functions); no direct impact on availability per the CVSS vector.

Affected software

  • Adobe Commerce: versions 2.4.4 through 2.4.9 (up to and including the July 2026 security releases, e.g. 2.4.9-2026-jul, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug, 2.4.5-2026-aug, 2.4.4-2026-aug)
  • Adobe Commerce B2B: versions 1.3.3 through 1.5.3 (up to and including 2026-jul releases)
  • Magento Open Source: versions 2.4.6 through 2.4.9 (up to and including 2026-jul releases)

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Adobe Commerce, Adobe Commerce B2B, and Magento Open Source to the August 2026 patch releases (e.g., 2.4.9-2026-aug and later, or the corresponding patched version for your branch) as published in Adobe Security Bulletin APSB26-92.
  • If no patch can be applied immediately: Restrict administrative and application network exposure where feasible, monitor for anomalous authorization/privilege-related activity, and prioritize patching given the unauthenticated, network-exploitable nature of this issue.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge