dbcve.org
CommerceApplication · Adobe

CVE-2026-21360

MEDIUM · 6.8 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 1.3.3 / 2.4.4 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Adobe Commerce contains a path traversal vulnerability allowing high-privileged attackers to access files outside restricted directories. The vulnerability exists in multiple versions (2.4.4-p16 through 2.4.9-alpha3) and enables unauthorized file/directory access without user interaction.

MitigationApply vendor-provided security patches for the affected Adobe Commerce versions, or upgrade to a patched version. Additionally, implement strict input validation on file path parameters to prevent directory traversal sequences.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CommerceApplication
Affected:< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9
Commerce B2bApplication
Affected:< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.2= 1.5.3
MagentoCMS
Affected:< 2.4.5= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Adobe Commerce version
    Check the composer.json file in the Magento root directory for the version entry under 'require' > 'magento/product-community-edition', or access the admin panel and navigate to System > About System to view the installed version.
    Affected if The installed version is 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, 2.4.9, or any version lower than 2.4.4
  2. Identify installed Adobe Commerce B2b version
    Check the composer.json for 'magento/module-b2b' version entry, or look in the admin panel under Stores > Settings > Configuration > B2B Features if the B2B module is enabled.
    Affected if The installed B2b version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.2, 1.5.3, or any version lower than 1.3.3
  3. Identify installed Adobe Magento version
    Check the composer.json for 'magento/magento2-base' version, or view the version from the admin panel at System > About System.
    Affected if The installed Magento version is 2.4.5, 2.4.6, 2.4.7, 2.4.8, 2.4.9, or any version lower than 2.4.5
  4. Confirm the vulnerability scope
    This CVE affects the file system layer in Adobe Commerce. Verify that any custom or third-party modules handling file paths (such as export, import, or media handling features) are in use on the system.
    Affected if The installation uses file handling features and the version falls within the affected ranges listed above

You are affected if your Adobe Commerce, Adobe Commerce B2b, or Adobe Magento installation matches any of the specific versions listed in the affected products and versions, as this path traversal vulnerability allows high-privileged attackers to access files outside restricted directories.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.3.3 / 2.4.4 / 2.4.5 or later
Fixed in 1.3.32.4.42.4.5
Interim mitigation

Apply vendor-provided security patches for the affected Adobe Commerce versions, or upgrade to a patched version. Additionally, implement strict input validation on file path parameters to prevent directory traversal sequences.

Recommended fix High confidence

Apply vendor security patch: 2.4.4-p16 (for 2.4.4.x), 2.4.5-p15 (for 2.4.5.x), 2.4.6-p13 (for 2.4.6.x), 2.4.7-p8 (for 2.4.7.x), or 2.4.8-p3 (for 2.4.8.x); or upgrade to 2.4.9-alpha3 or later stable release

  1. 1. Identify your current Adobe Commerce/Magento version by checking the composer.json file or the admin panel.
  2. 2. Access the Adobe Commerce security patch catalog at helpx.adobe.com to download the appropriate security patch for your version.
  3. 3. For Adobe Commerce 2.4.4.x: Apply patch CE-2.4.4-p16 or later.
  4. 4. For Adobe Commerce 2.4.5.x: Apply patch CE-2.4.5-p15 or later.
  5. 5. For Adobe Commerce 2.4.6.x: Apply patch CE-2.4.6-p13 or later.
  6. 6. For Adobe Commerce 2.4.7.x: Apply patch CE-2.4.7-p8 or later.
  7. 7. For Adobe Commerce 2.4.8.x: Apply patch CE-2.4.8-p3 or later.
  8. 8. For Commerce B2B 1.3.3.x-1.3.5.x: Apply the corresponding Commerce patch as B2B inherits Commerce patches.
Caveat Security patches typically have low risk but always test in staging first as they may include other bug fixes that could affect customizations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21360 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data