dbcve.org
CommerceApplication · Adobe

CVE-2026-21282

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 Improper Input Validation vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability by providing specially crafted input, causing limited impact to application availability. 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 improper input validation vulnerability in multiple versions (2.4.4-p16 through 2.4.9-alpha3) that allows unauthenticated attackers to submit specially crafted input leading to application denial-of-service. The vulnerability is network-exploitable with no user interaction required, leveraging insufficient validation of user-supplied data to cause a limited availability impact.

MitigationApply the appropriate Adobe Commerce security patch for this vulnerability (specific patch versions should be obtained from Adobe's official security bulletin) and implement additional input validation safeguards at the application boundary to reject malformed requests before processing.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

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

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 CLI version
    Run `bin/magento --version` or `php bin/magento --version` from the Magento root directory
    Affected if The version output is 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9 (any patch version within 2.4.4-p16 through 2.4.9) or is earlier than 2.4.4
  2. Check composer.json for installed version
    Inspect the `composer.json` file in the Magento root directory and look for the `version` field under the `extra` section or check `composer.lock` for the magento/project-community-edition or magento/project-enterprise-edition package version
    Affected if The resolved package version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9 or is earlier than 2.4.4
  3. Check Adobe Commerce B2B module version
    Run `bin/magento module:status` and look for Magento_CompanyBundle or check composer.lock for magento/module-b2b-enterprise-edition version
    Affected if The B2B module version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.2, or 1.5.3 or earlier than 1.3.3
  4. Verify admin panel version display
    Log into the Adobe Commerce admin panel and check the footer area or navigate to System > Configuration > Advanced > Advanced and look for version information
    Affected if The displayed version matches the affected ranges listed above

The environment is affected if Adobe Commerce, Magento, or B2B module version is within 2.4.4 through 2.4.9 (or earlier than 2.4.4) or if the B2B module version is 1.3.3 or later within the listed vulnerable versions.

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 the appropriate Adobe Commerce security patch for this vulnerability (specific patch versions should be obtained from Adobe's official security bulletin) and implement additional input validation safeguards at the application boundary to reject malformed requests before processing.

Recommended fix Moderate confidence

Upgrade to the latest patch version in your release line (e.g., 2.4.4-p17+, 2.4.5-p16+, 2.4.6-p14+, 2.4.7-p9+, 2.4.8-p4+) or move to the latest stable 2.4.7 release

  1. 1. Identify your current Adobe Commerce/Magento version using the admin panel or command line (bin/magento --version)
  2. 2. For Magento 2.4.4: Upgrade to 2.4.4-p17 or later (or to 2.4.7-p9 or later for major version change)
  3. 3. For Magento 2.4.5: Upgrade to 2.4.5-p16 or later (or to 2.4.7-p9 or later for major version change)
  4. 4. For Magento 2.4.6: Upgrade to 2.4.6-p14 or later (or to 2.4.7-p9 or later for major version change)
  5. 5. For Magento 2.4.7: Upgrade to 2.4.7-p9 or later
  6. 6. For Magento 2.4.8: Upgrade to 2.4.8-p4 or later
  7. 7. For Adobe Commerce B2b, apply the corresponding Adobe Commerce patch alongside the core upgrade
  8. 8. Run bin/magento setup:upgrade after upgrade to apply database migrations
Caveat Standard Adobe Commerce patch upgrades typically have minimal breaking changes; however, always review release notes for your target version for any known compatibility issues with custom modules or extensions

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

Fix this in Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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