dbcve.org
CommerceApplication · Adobe

CVE-2026-34645

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 an Incorrect Authorization vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized write access. 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 an Incorrect Authorization vulnerability allowing attackers to bypass security measures and gain unauthorized write access. The vulnerability affects multiple versions (2.4.4-p17 through 2.4.9-beta1) and can be exploited without any user interaction.

MitigationApply the available security patches provided by Adobe for the specific Commerce version in use, or upgrade to a patched version as indicated in Adobe's security bulletin.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Determine Adobe Commerce version
    Run the command: php bin/magento --version or check the composer.json file for the magento/product-community-edition or magento/enterprise-edition version entry
    Affected if The installed version matches any of these: < 2.4.4, = 2.4.4, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8, = 2.4.9, or is less than 2.4.4-p17 in the 2.4.4 patch line
  2. Check if Adobe Commerce B2B module is installed
    Run the command: php bin/magento module:status | grep Magento_B2b or check composer.json for magento/module-b2b version
    Affected if The B2B module is installed and its version matches any of: < 1.3.3, = 1.3.3, = 1.3.4, = 1.4.2, = 1.5.2, = 1.5.3, or is less than 1.3.3-p1 in the 1.3.3 patch line
  3. Check if Magento Open Source version is in use
    Run: php bin/magento --version or inspect composer.json for magento/project-community-edition version entry
    Affected if The installed version matches any of: < 2.4.6, = 2.4.6, = 2.4.7, = 2.4.8, = 2.4.9, or is less than 2.4.6-p7 in the 2.4.6 patch line

Your environment is affected if you are running any Adobe Commerce, Commerce B2b, or Magento Open Source installation with a version that falls within the affected ranges listed above.

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 available security patches provided by Adobe for the specific Commerce version in use, or upgrade to a patched version as indicated in Adobe's security bulletin.

Recommended fix Moderate confidence

Adobe Commerce 2.4.8-p5 or later / Magento 2.4.8-p5 or later / Commerce B2b 1.4.3 or later

  1. 1. Identify your current Adobe Commerce/Magento installation version using the command line or admin panel.
  2. 2. Backup your entire Magento database and filesystem before performing any upgrade.
  3. 3. Enable maintenance mode: php bin/magento maintenance:enable
  4. 4. Run composer to update to the latest patched version: composer require magento/product-community-edition=2.4.8-p5 --no-update (or the latest available patched release from security patch APSB26-XX)
  5. 5. Update composer dependencies: composer update
  6. 6. Clear the cache and regenerate the di compilation: rm -rf var/di/* var/cache/* var/page_cache/* var/generated/*
  7. 7. Run the upgrade script: php bin/magento setup:upgrade
  8. 8. Re-compile dependency injection: php bin/magento setup:di:compile
Caveat Review Adobe Commerce upgrade documentation for breaking changes between your current version and 2.4.8; potential impacts include theme/template modifications, third-party extension compatibility, and PHP version requirements.

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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