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. An attacker could leverage this vulnerability to bypass security measures and have limited impact to the integrity and availability of data. The exploit depends on conditions beyond the attacker's control. Exploitation of this issue does not require user interaction.
Security readout for executives and security teams
Plain-English summary
This authorization flaw can let a remote attacker bypass a security control, causing limited data changes or service disruption. Adobe rates it medium severity. Exploitation is difficult because it requires conditions outside the attacker’s control, but no user interaction is described as necessary.
Executive priority
Schedule prompt remediation through normal vulnerability management rather than emergency response. Raise priority for internet-facing commerce systems, sensitive transactions, or deployments lacking compensating controls. Escalate immediately if Adobe or another cited authority later confirms exploitation.
Technical view
CVE-2026-21359 is a CWE-863 incorrect-authorization issue affecting specified Adobe Commerce releases and potentially related listed products. CVSS 3.1 is 4.7: network-reachable, high complexity, no privileges, changed scope, no confidentiality impact, and low integrity and availability impact. The supplied narrative and CVSS vector disagree about user interaction.
Likely exposure
Internet-reachable deployments running the affected Adobe Commerce versions are the clearest concern. The bundle also lists Adobe Commerce B2B and Magento Open Source, but its structured version ranges are ambiguous. Confirm each installed product, edition, branch, and patch level against Adobe’s advisory.
Exploitation context
The bundle provides no cited evidence of active exploitation, and the CVE is not listed as KEV. Exploitation requires conditions beyond the attacker’s control. The description says no user interaction, while the supplied CVSS vector contains UI:R; defenders should resolve this discrepancy using Adobe’s advisory.
Researcher notes
The source bundle contains a material inconsistency: the narrative states exploitation requires no user interaction, but CVSS includes UI:R. It also presents structured product-version boundaries without explaining whether they are affected or fixed thresholds. Use Adobe’s advisory as the controlling source before final exposure classification.
Mitigation direction
Review Adobe advisory APSB26-05 for the approved remediation applicable to each deployed product branch.
Upgrade affected installations to an Adobe-designated non-affected release after normal compatibility and rollback testing.
Follow any Adobe compensating-control guidance when immediate upgrading is not operationally possible.
Validation and detection
Inventory Adobe Commerce, Commerce B2B, and Magento Open Source editions and exact patch levels.
Compare every deployment version directly with APSB26-05 because the supplied structured ranges are ambiguous.
Confirm the remediation through authenticated version or package records after deployment.
Review security monitoring for unexplained authorization bypasses, data modifications, or service disruption.
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.