dbcve.org
CommerceApplication · Adobe

CVE-2026-34654

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-12
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-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, 2.4.4-p17 and earlier are affected by a Dependency on Vulnerable Third-Party Component vulnerability that could result in an application denial-of-service. An attacker could exploit this vulnerability to crash the application, leading to a denial-of-service condition. 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 versions 2.4.4-p17 through 2.4.9-beta1 include a vulnerable third-party dependency that can be exploited without authentication to cause application crashes, resulting in denial-of-service. This is a transitive dependency vulnerability where the application's reliance on an insecure library creates the attack surface.

MitigationApply the vendor-supplied security patches or update Adobe Commerce to a version beyond the affected releases listed. Identify the specific vulnerable component through Adobe's security advisory and verify the fix does not break existing functionality.

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.4.2= 1.5.2= 1.5.3
MagentoCMS
Affected:< 2.4.6= 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 version
    Run command: bin/magento --version or check composer.json for the 'magento/product-community-edition' or 'magento/product-enterprise-edition' version entry
    Affected if Version is 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9, or any version below 2.4.4
  2. Check Adobe Magento version
    Run command: bin/magento --version or check composer.json for the 'magento/community-edition' version entry
    Affected if Version is 2.4.6, 2.4.7, 2.4.8, or 2.4.9, or any version below 2.4.6
  3. Check Adobe Commerce B2b version
    Check composer.json for the 'magento/module-b2b' or 'magento/extension-b2b' version entry, or run: bin/magento config:show b2b_extension_version 2>/dev/null
    Affected if Version is 1.3.3, 1.3.4, 1.4.2, 1.5.2, or 1.5.3, or any version below 1.3.3
  4. Confirm vulnerability context
    Verify the application uses the vulnerable third-party component by reviewing composer.lock for the affected library name if disclosed in Adobe security advisory
    Affected if The vulnerable transitive dependency is present in the dependency tree

You are affected if your Adobe Commerce, Magento, or Commerce B2b installation matches any of the version ranges listed, as the vulnerable third-party dependency is included in those releases.

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.6 or later
Fixed in 1.3.32.4.42.4.6
Interim mitigation

Apply the vendor-supplied security patches or update Adobe Commerce to a version beyond the affected releases listed. Identify the specific vulnerable component through Adobe's security advisory and verify the fix does not break existing functionality.

Recommended fix Moderate confidence

Adobe Commerce 2.4.7-p9 or later (or latest 2.4.x release); Magento 2.4.6-p14 or later

  1. 1. Identify your current Adobe Commerce/Magento version by running: bin/magento --version
  2. 2. For Commerce versions < 2.4.4: Upgrade to the latest 2.4.x release (at least 2.4.7-p9 or later)
  3. 3. For Commerce version 2.4.4: Upgrade to at least 2.4.4-p17 or later
  4. 4. For Commerce version 2.4.5: Upgrade to at least 2.4.5-p16 or later
  5. 5. For Commerce version 2.4.6: Upgrade to at least 2.4.6-p14 or later
  6. 6. For Magento versions < 2.4.6: Upgrade to at least 2.4.6-p14 or later
  7. 7. For Magento versions 2.4.6, 2.4.7: Upgrade to latest patch or 2.4.8-p4 or later
  8. 8. For Commerce B2b < 1.3.3: Upgrade to 1.3.3-p3 or later
Caveat Review Adobe Commerce upgrade documentation for compatibility notes; major version upgrades may require code changes

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

Fix this in Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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