dbcve.org
Commerce B2bApplication · Adobe

CVE-2026-21286

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Incorrect Authorization vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain limited unauthorized view access of data. 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 · moderate confidence

Adobe Commerce contains an Incorrect Authorization vulnerability allowing attackers to bypass security measures and gain limited unauthorized view access to certain data. The issue stems from improper authorization checks that can be exploited without user interaction.

MitigationUpgrade Adobe Commerce to the latest patched version (2.4.9 or later for 2.4.x releases). Review and audit existing access control configurations to ensure the bypass is fully mitigated.

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
Commerce B2bApplication
Affected:< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.2= 1.5.3
CommerceApplication
Affected:< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9
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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Check Adobe Commerce version via CLI
    Run `bin/magento --version` or `composer show magento/product-community-edition 2>/dev/null | grep version` in the Magento root directory
    Affected if The version is less than 2.4.4, or equals 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9
  2. Check Adobe Magento Open Source version via CLI
    Run `bin/magento --version` or `composer show magento/magento2-base 2>/dev/null | grep version` in the Magento root directory
    Affected if The version is less than 2.4.5, or equals 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9
  3. Check Adobe Commerce B2B module version
    Run `bin/magento module:status Magento_B2b` or `composer show magento/module-b2b 2>/dev/null | grep version` if the B2B module is installed
    Affected if The B2B module is installed and its version is less than 1.3.3, or equals 1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.2, or 1.5.3
  4. Confirm deployment type
    Check if the instance is running Adobe Commerce (commercial) or Magento Open Source by inspecting the license file or checking for commercial modules: `composer show magento/magento-enterprise-base 2>/dev/null`
    Affected if The instance is Adobe Commerce and the version falls within the affected Commerce ranges listed above

You are affected if your Adobe Commerce or Magento Open Source installation version matches any of the affected version ranges listed in the CVE, which exposes the incorrect authorization vulnerability allowing unauthorized view access.

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

Upgrade Adobe Commerce to the latest patched version (2.4.9 or later for 2.4.x releases). Review and audit existing access control configurations to ensure the bypass is fully mitigated.

Recommended fix High confidence

Adobe Commerce/Magento 2.4.9 or later (or at minimum 2.4.7-p9, 2.4.8-p4, 2.4.6-p14, 2.4.5-p16, 2.4.4-p17 depending on your baseline branch); Adobe Commerce B2B 1.3.6 or later

  1. 1. Verify current Adobe Commerce/Magento installation version by running: php bin/magento --version
  2. 2. Review current system requirements and backup the database and codebase before upgrading
  3. 3. For Adobe Commerce (Commerce) users: Upgrade to version 2.4.7-p9 or later, or preferably 2.4.9 or later
  4. 4. For Adobe Commerce B2B users: Upgrade to version 1.3.6 or later
  5. 5. For Magento Open Source users: Upgrade to version 2.4.7-p9 or later, or preferably 2.4.9 or later
  6. 6. After upgrade, clear the cache: php bin/magento cache:flush
  7. 7. Reindex: php bin/magento indexer:reindex
  8. 8. Verify the upgrade was successful and the version is no longer in the affected list
Caveat Major version upgrades may introduce breaking changes; review Adobe's upgrade documentation and release notes for compatibility considerations with custom extensions and themes before proceeding

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

Fix this in Commerce B2b Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21286 — 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-21286 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