CVE-2026-21360: Adobe Commerce | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (CWE-22)
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 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could result in a security feature bypass. A high-privileged attacker could leverage this vulnerability to access unauthorized files or directories outside the intended restricted path. Exploitation of this issue does not require user interaction.
Security readout for executives and security teams
Plain-English summary
This flaw may let a highly privileged attacker bypass a file-access boundary and read files outside an intended directory. It can be exploited remotely without user action, but the attacker must already possess high privileges. The primary stated risk is exposure of confidential information, not data alteration or service disruption.
Executive priority
Treat this as prompt, risk-based remediation rather than an automatic emergency. Accelerate action where sensitive files are accessible to the application, privileged access is broadly assigned, or administrative access controls are weak. The high confidentiality impact warrants attention despite the high-privilege prerequisite.
Technical view
CVE-2026-21360 is a CWE-22 path-traversal vulnerability resulting in security-feature bypass and unauthorized file or directory access. Its CVSS 3.1 score is 6.8: network-accessible, low complexity, high privileges required, no user interaction, changed scope, high confidentiality impact, and no stated integrity or availability impact.
Likely exposure
Inventory Adobe Commerce, Adobe Commerce B2B, and Magento Open Source deployments, then confirm exact status through APSB26-05. The description identifies Adobe Commerce 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 releases as affected.
Exploitation context
The supplied sources do not report active exploitation or a public exploit, and the CVE is not identified as KEV-listed. Exploitation requires network access and high privileges but no user interaction. Absence from KEV does not establish that exploitation has never occurred.
Researcher notes
The CVSS vector indicates no demonstrated integrity or availability impact. The supplied affected-version representation is not fully self-explanatory, particularly across product branches; consult APSB26-05 before declaring a deployment affected or fixed. No root cause, proof of concept, detection signature, or observed exploitation evidence is included.
Mitigation direction
Check APSB26-05 for the vendor-designated corrected release for every deployed branch.
Upgrade affected deployments after testing storefront, administration, extensions, and integrations.
Reduce unnecessary high-privileged access until remediation is complete.
Protect privileged accounts with strong authentication and review their current assignments.
Validation and detection
Record product, edition, and version across production, staging, and recovery environments.
Compare every deployed version with Adobe's APSB26-05 affected and corrected release information.
Review privileged-account activity and available file-access telemetry for unexpected access patterns.
After upgrading, verify the running version and retest application access controls and critical workflows.
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-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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.