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 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.
Security readout for executives and security teams
Plain-English summary
A remote attacker can exhaust an affected Adobe Commerce store’s computing resources, making the application unavailable without requiring user action. The documented impact is service disruption, not theft or modification of data. Publicly reachable commerce sites face the greatest business risk from lost sales and interrupted operations.
Executive priority
Treat as a high-priority availability risk for revenue-generating or customer-facing stores. Establish exposure quickly, schedule the Adobe-supported update, and ensure operational monitoring can detect resource exhaustion. Escalate internet-exposed affected systems ahead of internal or isolated deployments.
Technical view
CVE-2026-34651 is a CWE-400 uncontrolled resource consumption flaw with CVSS 3.1 score 7.5. The vector indicates network access, low complexity, no privileges, and no user interaction. Successful exploitation causes high availability impact while documented confidentiality and integrity impacts are none.
Likely exposure
Exposure is most likely where affected Adobe Commerce releases are reachable over a network, especially public storefronts. The description identifies 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 as affected. The structured B2B and Magento version data is ambiguous; confirm applicability with Adobe.
Exploitation context
Exploitation requires no authentication or user interaction and is rated low complexity. The source bundle marks the CVE as absent from CISA KEV and provides no evidence of active exploitation. Absence from KEV does not establish that exploitation has never occurred.
Researcher notes
The weakness is CWE-400 and the CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. The bundle does not identify the vulnerable component, triggering request, exploitation volume, or specific resource exhausted. Structured product-version entries appear compressed or ambiguous, so authoritative applicability and fixed-release interpretation should come from APSB26-49.
Mitigation direction
Inventory Adobe Commerce, Commerce B2B, and Magento Open Source deployments and record exact versions.
Review Adobe advisory APSB26-49 for the applicable vendor-supported update.
Prioritize updating public storefronts and other network-accessible deployments.
Use capacity controls and monitoring as temporary risk reduction, not substitutes for vendor remediation.
Validation and detection
Compare every deployment version with Adobe advisory APSB26-49.
Confirm updated systems report the intended vendor-supported release.
Verify public and partner-facing exposure through approved asset inventory and configuration records.
Monitor application availability, resource saturation, and abnormal request spikes.
Perform controlled resilience testing without reproducing offensive exploitation techniques.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.