Adobe Commerce versions 2.4.9-alpha3, 2.4.8-p3, 2.4.7-p8, 2.4.6-p13, 2.4.5-p15, 2.4.4-p16 and earlier are affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain limited unauthorized access to a feature. Exploitation of this issue does not require user interaction.
Security readout for executives and security teams
Plain-English summary
A user with limited privileges may bypass an authorization check and gain limited, unauthorized access to an Adobe Commerce feature. No user interaction is required. The reported impact is confined to limited confidentiality exposure, with no stated integrity or availability impact.
Executive priority
Schedule remediation through the normal vulnerability-management cycle, prioritizing internet-facing stores and environments with many low-privileged accounts. Escalate if monitoring identifies unauthorized feature access or vendor guidance reports exploitation.
Technical view
CVE-2026-21285 is a network-accessible incorrect-authorization flaw (CWE-863). Exploitation requires low privileges, has low complexity, and requires no victim interaction. Its CVSS 3.1 score is 4.3 (medium), reflecting low confidentiality impact without stated integrity, availability, or scope impact.
Likely exposure
Potential exposure includes affected Adobe Commerce, Adobe Commerce B2B, and Magento Open Source installations below the unaffected version boundaries listed in the source bundle. Publicly reachable administrative or authenticated application surfaces may increase opportunity, but exploitation still requires a low-privileged account.
Exploitation context
The bundle reports no CISA KEV listing and provides no evidence of active exploitation. The flaw is remotely reachable and requires low privileges, low complexity, and no user interaction. Evidence does not establish exploit availability, attack prevalence, or the exact feature exposed.
Researcher notes
The supplied data identifies incorrect authorization but does not name the affected feature or authorization path. Version notation differs between the narrative and structured boundaries, so verify applicability against APSB26-05. Avoid interpreting absence from KEV as proof that exploitation has not occurred.
Mitigation direction
Inventory Adobe Commerce, Commerce B2B, and Magento Open Source versions.
Compare installed releases with the unaffected version boundaries in the CVE record.
Apply the appropriate vendor-supported security release after confirming edition and branch applicability.
Review Adobe advisory APSB26-05 for deployment requirements and additional guidance.
Validation and detection
Confirm the installed product edition, core version, and B2B extension version where applicable.
Verify production instances meet or exceed the applicable unaffected boundary.
Test authorization boundaries using approved low-privilege accounts after updating.
Review access records for unusual low-privilege use of restricted features.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.