dbcve.org
CommerceApplication · Adobe

CVE-2026-34647

HIGH · 7.4 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 →
81/100
Remediation priority · High
Remotely reachable No privileges

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 Server-Side Request Forgery (SSRF) vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized read access. Exploitation of this issue requires user interaction in that a victim must visit a maliciously crafted URL or interact with a compromised web page. Scope is changed.

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 Server-Side Request Forgery (SSRF) vulnerability allowing attackers to make the server perform unauthorized requests to internal or external resources. This security feature bypass enables unauthorized read access to potentially sensitive data or internal services. The vulnerability requires user interaction, specifically that a victim visits a maliciously crafted URL or interacts with a compromised page.

MitigationApply the appropriate Adobe security patch or upgrade to a fixed version (2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, or 2.4.4-p17 and later) to remediate this SSRF vulnerability.

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
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm Adobe Commerce or Magento installation
    Check for the presence of Magento/Adobe Commerce by looking for app/etc/env.php or vendor/magento directory, and check the admin panel footer for version display or run: bin/magento --version
    Affected if The system is running Adobe Commerce or Magento (not MagenTo Open Source)
  2. Determine the installed Adobe Commerce version
    Run command: bin/magento --version or check composer.json for 'version' field under 'require' for 'magento/product-community-edition' or 'magento/product-enterprise-edition'
    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 lower than 2.4.4
  3. Check for Adobe Commerce B2B extension version if installed
    Run: composer show magento/module-b2b 2>/dev/null | grep -i version, or check composer.json for 'magento/module-b2b' version
    Affected if B2B module is installed and version is 1.3.3, 1.3.4, 1.4.2, 1.5.2, or 1.5.3, or any version lower than 1.3.3
  4. Identify if this is Adobe Magento (not Commerce)
    Check composer.json for 'magento/magento2-base' or 'magento/product-community-edition' vs 'magento/product-enterprise-edition' (Commerce)
    Affected if Running Magento (not Commerce) with version 2.4.6, 2.4.7, 2.4.8, or 2.4.9, or any version below 2.4.6
  5. Verify the SSRF-prone feature is accessible
    Review admin configuration for any modules that perform external HTTP requests (check under Stores > Configuration > Advanced > System for transport or HTTP client settings)
    Affected if External request features are enabled and accessible to users who could be tricked into visiting malicious URLs

The environment is affected if it runs Adobe Commerce versions 2.4.4 through 2.4.9 (or below 2.4.4), Adobe Commerce B2B versions 1.3.3 through 1.5.3 (or below 1.3.3), or Magento versions 2.4.6 through 2.4.9 (or below 2.4.6), and the system allows external request features to be triggered via user interaction.

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 appropriate Adobe security patch or upgrade to a fixed version (2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, or 2.4.4-p17 and later) to remediate this SSRF vulnerability.

Recommended fix Moderate confidence

Upgrade to the latest available patch version for your respective release line (e.g., 2.4.4-p18, 2.4.5-p17, 2.4.6-p15, 2.4.7-p10, 2.4.8-p5, or later)

  1. 1. Identify the currently installed Adobe Commerce/Magento version by checking the composer.json file or running `bin/magento --version`
  2. 2. Based on your current version line, upgrade to the latest available patch version that addresses this vulnerability
  3. 3. For Magento 2.4.4.x users: upgrade to 2.4.4-p18 or later
  4. 4. For Magento 2.4.5.x users: upgrade to 2.4.5-p17 or later
  5. 5. For Magento 2.4.6.x users: upgrade to 2.4.6-p15 or later
  6. 6. For Magento 2.4.7.x users: upgrade to 2.4.7-p10 or later
  7. 7. For Magento 2.4.8.x users: upgrade to 2.4.8-p5 or later
  8. 8. Run `composer update` to apply the new packages
Caveat Patch updates are generally backward compatible; however, test in a staging environment before deploying to production as custom extensions or themes may be affected

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

Fix this in Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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