CVE-2026-34651
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 · uneditedAdobe 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 Uncontrolled Resource Consumption vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability to exhaust system resources, resulting in an application 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 · high confidenceAdobe Commerce versions 2.4.9-beta1 through 2.4.4-p17 and earlier contain an Uncontrolled Resource Consumption (CWE-400) vulnerability that allows unauthenticated attackers to exhaust system resources and cause denial-of-service without any user interaction.
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< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9< 1.3.3= 1.3.3= 1.3.4= 1.4.2= 1.5.2= 1.5.3< 2.4.6= 2.4.6= 2.4.7= 2.4.8= 2.4.9CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine Adobe Commerce installed versionRun 'bin/magento --version' from the Magento root directory, or check the version shown in the admin panel footer, or inspect composer.json for the 'magento/product-community-edition' versionAffected if The version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9 (including beta and patch versions like -p17 or earlier), or is earlier than 2.4.4
-
Determine Adobe Commerce B2B module versionRun 'bin/magento module:status' to list modules, or check composer.json for 'magento/module-b2b-core' version if B2B is installedAffected if B2B module version is 1.3.3, 1.3.4, 1.4.2, 1.5.2, 1.5.3, or earlier than 1.3.3
-
Confirm Adobe Magento installation typeIdentify if the installation is Adobe Magento (not Adobe Commerce) by checking the edition in composer.json or admin panelAffected if The installation uses Adobe Magento (not Commerce) and version is 2.4.6, 2.4.7, 2.4.8, 2.4.9, or earlier than 2.4.6
-
Check if web interface is exposedVerify the Magento storefront and admin are accessible over HTTP/HTTPS from the networkAffected if The web interface is externally accessible, as the vulnerability allows unauthenticated remote attackers to exhaust resources without user interaction
The environment is affected if it runs any Adobe Commerce, Adobe Commerce B2B, or Adobe Magento version within the ranges listed, and the web interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.3.32.4.42.4.6
Apply the vendor-provided security patch or upgrade to a patched version of Adobe Commerce (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) after testing in a staging environment.
Upgrade to the latest stable 2.4.7 or 2.4.8 release (e.g., 2.4.7-p10+, 2.4.8-p5+) and corresponding B2B version (1.3.5+, 1.4.3+)
- 1. Identify the current Adobe Commerce/Magento version by running: php bin/magento --version or checking composer.json
- 2. For Adobe Commerce 2.4.4: Upgrade to 2.4.4-p18 or later by running: composer require magento/product-community-edition=2.4.4-p18 --no-update && composer update
- 3. For Adobe Commerce 2.4.5: Upgrade to 2.4.5-p17 or later by running: composer require magento/product-community-edition=2.4.5-p17 --no-update && composer update
- 4. For Adobe Commerce 2.4.6: Upgrade to 2.4.6-p15 or later by running: composer require magento/product-community-edition=2.4.6-p15 --no-update && composer update
- 5. For Adobe Commerce 2.4.7: Upgrade to 2.4.7-p10 or later by running: composer require magento/product-community-edition=2.4.7-p10 --no-update && composer update
- 6. For Adobe Commerce 2.4.8: Upgrade to 2.4.8-p5 or later by running: composer require magento/product-community-edition=2.4.8-p5 --no-update && composer update
- 7. For Adobe Commerce B2B 1.3.3/1.3.4: Upgrade to 1.3.5 or later by running: composer require magento/module-b2b=1.3.5 --no-update && composer update
- 8. For Adobe Commerce B2B 1.4.2: Upgrade to 1.4.3 or later by running: composer require magento/module-b2b=1.4.3 --no-update && composer update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34651 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34651 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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