CVE-2026-71362

CRITICAL(9.1)KEVLikely Exploited

Adobe Commerce and Magento Incorrect Authorization Vulnerability

Description

CVE-2026-71362 is a critical incorrect authorization vulnerability in Adobe Commerce and Magento that results in privilege escalation: an unauthenticated attacker can gain elevated access to sensitive resources without any user interaction. The affected range covers Adobe Commerce up to 2.4.9, Adobe Commerce B2B up to 1.5.3 and Magento up to 2.4.9, which is close to the entire current installed base of the platform. Online shops are an immediate monetization target — customer data, order records and payment flows all sit behind the authorization check that this vulnerability defeats. CISA has added CVE-2026-71362 to the Known Exploited Vulnerabilities catalog, its EPSS score of 87.5% places it in the 99.8th percentile, among the most actively exploited vulnerabilities anywhere, and the remediation deadline of September 27, 2026 has already passed.

KEV Information

Vendor
Adobe
Product
Commerce and Magento
Date Added
September 24, 2026
Due Date
September 27, 2026
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.

CVSS Score

Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NOpen in Calculator
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
NONE
Exploitability Score
3.9
Impact Score
5.2

CWEs

Affected Products

VendorProductVersion
adobecommerce< 2.4.4; 2.4.4; 2.4.5; 2.4.6; 2.4.7; 2.4.8; 2.4.9
adobecommerce b2b< 1.3.3; 1.3.3; 1.3.4; 1.4.2; 1.5.2; 1.5.3
adobemagento<= 2.4.6; 2.4.7; 2.4.8; 2.4.9

References

Weakness Type

CWE-863: Incorrect Authorization

Incorrect authorization describes a check that exists but does not work — the wrong role is examined, the comparison logic is flawed, an edge case is missed, or a cached decision outlives the permission it reflected. This is distinct from a missing check entirely. In Adobe Commerce and Magento, the authorization performed before access to sensitive resources is implemented incorrectly, so a request that should have been rejected is granted elevated access instead.

Learn more: CWE-863 — Incorrect Authorization

Impact Analysis

CVE-2026-71362 has a CVSS 3.1 base score of 9.1 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N — note that the published vector records no integrity or availability impact, while Adobe describes the outcome as privilege escalation granting elevated access to sensitive resources. Attack Vector (Network), Privileges Required (None), User Interaction (None), Attack Complexity (Low): the request comes from the internet, needs no account, needs no victim and works reliably — the complete absence of preconditions is what drives both the 9.1 score and the extraordinary EPSS value. Confidentiality (High): an e-commerce platform's sensitive resources are customer records, order and address data, and administrative functionality; unauthorized elevated access to them is a data breach in the regulatory sense and, in most jurisdictions, notifiable. For merchants, the second-order consequences are as serious as the first: shops in this product family have historically been targeted with payment-skimming code once attackers gain a foothold. With an EPSS score of 87.5% and a lapsed KEV deadline, an unpatched store should be assumed to have been attacked.

Exploit Maturity

CISA has added CVE-2026-71362 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the remediation deadline of September 27, 2026 has already passed; the entry does not flag use in ransomware campaigns. The references are Adobe Security Bulletin APSB26-92 and the CISA catalog entry rather than exploit code, so no public proof-of-concept appears in the reference set — but the EPSS score makes that detail nearly irrelevant. At 87.5%, in the 99.8th percentile, this is among the handful of vulnerabilities the model considers near-certain to be exploited, and the figure is consistent with how this platform is attacked: Magento and Adobe Commerce stores are enumerated continuously by automated scanners, and unauthenticated privilege escalation flaws in them have historically been weaponized within days and used to inject payment skimmers. Any store that ran an affected version while reachable should be investigated for compromise, not simply updated.

Remediation

  1. Carry out the action CISA requires, immediately. Apply mitigations in accordance with Adobe's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV remediation deadline of September 27, 2026 has already passed.
  2. Apply the Adobe security update described in Adobe Security Bulletin APSB26-92. Affected are Adobe Commerce through 2.4.9, Adobe Commerce B2B through 1.5.3 and Magento through 2.4.9, including versions below 2.4.4 that may already be out of support — those need migration to a supported release rather than a patch.
  3. Treat the shop as compromised and hunt for skimmers. Given the EPSS score and the passed deadline, review the webroot and the database for injected JavaScript in CMS blocks, pages and layout XML, compare core files against official checksums, look for new administrator accounts and integration tokens, and inspect recently modified templates. Payment-skimming code in this platform family is typically small and placed in content records rather than in files.
  4. Rotate every credential the installation holds. Change administrator passwords, invalidate admin sessions, regenerate the encryption key, rotate API and integration tokens, database credentials and payment gateway keys, since elevated access may have exposed them.
  5. Reduce the exposed surface and verify authorization. Keep the admin panel on a restricted path behind IP allowlisting or a VPN, enable two-factor authentication for all administrators, and — as the general lesson for this weakness class — centralize authorization decisions in well-tested framework code, deny by default, and test the edge cases and role boundaries rather than only the happy path.

Technical Details

Adobe describes CVE-2026-71362 as an incorrect authorization vulnerability leading to privilege escalation, with elevated access to sensitive resources and no user interaction required. The CWE-863 classification is precise about the nature of the defect: an authorization check is performed, but its implementation does not correctly establish whether the requester is entitled to the resource — the typical causes being evaluation against the wrong identity or role, flawed comparison logic, an unhandled edge case, or a decision that is reused when it should be re-evaluated. Because the check is present, the flaw is invisible to reviews that only ask whether authorization exists. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N records a remotely reachable, deterministic, unauthenticated path with high confidentiality impact and an unchanged scope — the attacker gains authority within the application rather than beyond it, but within an e-commerce platform that authority covers the customer and order data the shop exists to process.

Frequently Asked Questions

Is CVE-2026-71362 being actively exploited?

Yes. CISA has added CVE-2026-71362 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the remediation deadline of September 27, 2026 has already passed. Its EPSS score of 87.5% is in the 99.8th percentile, indicating near-certain exploitation activity. Use in ransomware campaigns is not recorded in the KEV entry.

What products are affected by CVE-2026-71362?

CVE-2026-71362 affects Adobe Commerce in versions up to and including 2.4.9 as well as releases below 2.4.4, Adobe Commerce B2B up to 1.5.3 and below 1.3.3, and Magento up to 2.4.9. Consult Adobe Security Bulletin APSB26-92 for the exact fixed version matching your release line.

How do I fix CVE-2026-71362?

Apply the Adobe security update per bulletin APSB26-92 for your Adobe Commerce, Commerce B2B or Magento version; installations on releases that have reached end of support need migration rather than a patch. Because the deadline has passed and exploitation is near-certain, also check the shop for injected skimmer code in CMS content and templates, review administrator accounts, and rotate admin passwords, API tokens, the encryption key and payment gateway credentials.

How severe is CVE-2026-71362?

CVE-2026-71362 is rated Critical with a CVSS 3.1 base score of 9.1: unauthenticated, remotely reachable privilege escalation with no user interaction and high confidentiality impact. Its EPSS score of 87.5% in the 99.8th percentile is exceptional and is the decisive number here — this is being exploited broadly. For a shop handling customer and order data, successful exploitation is a reportable data breach.

CVSS Score

9.1
CRITICAL(9.1)

EPSS Score

EPSS Score91.68%
EPSS Percentile99.8%

Dates

PublishedAugust 11, 2026
Last ModifiedOctober 26, 2026
StatusAnalyzed
CVSS Versionv3.1

Need Help With Vulnerability Management?

Our security experts can help you prioritize and remediate vulnerabilities effectively.