CVE-2026-34652: Adobe Commerce | Dependency on Vulnerable Third-Party Component (CWE-1395)
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.
Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker could crash vulnerable Adobe Commerce or Magento Open Source applications, disrupting storefront availability and business operations. The supplied CVSS score is 7.5 (High). The described impact is denial of service; the sources do not report data theft or modification.
Executive priority
Prioritize internet-facing and revenue-critical storefronts for prompt remediation. The documented consequence is service interruption rather than confidentiality or integrity loss, but unauthenticated remote reachability makes operational disruption credible. Accelerate change control where downtime would materially affect sales, customers, or contractual availability targets.
Technical view
CVE-2026-34652 is a vulnerable third-party dependency issue classified as CWE-1395. Its CVSS 3.1 vector indicates network access, low complexity, no privileges, no user interaction, unchanged scope, and high availability impact. The bundle identifies Adobe Commerce releases through 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, and 2.4.4-p17 as affected, plus 2.4.9-beta1.
Likely exposure
Internet-accessible storefronts running an affected release are the primary concern because exploitation is network-based and requires neither authentication nor user interaction. Internal or access-restricted deployments have reduced reachability but remain vulnerable. Confirm exact editions and versions because the structured version data also references Commerce B2B and Magento Open Source release lines.
Exploitation context
The supplied sources describe a low-complexity, unauthenticated denial-of-service condition. They provide no evidence of active exploitation, and the bundle marks KEV as false. This does not establish that exploitation is impossible or absent; it only means active exploitation is not supported by the supplied evidence.
Researcher notes
The bundle attributes the flaw to a vulnerable third-party component but does not identify that component or the precise triggering condition. Avoid inferring additional impacts. Validate product-specific boundaries directly against APSB26-49, particularly because the structured affected data includes multiple product and release lines whose encoding is not fully explained in the prompt.
Mitigation direction
Review Adobe advisory APSB26-49 for the applicable corrected release.
Upgrade affected Adobe Commerce and Magento Open Source installations using Adobe-supported procedures.
Restrict unnecessary network access until remediation is complete.
Use availability monitoring and rate controls as temporary risk reduction, not substitutes for updating.
Validation and detection
Inventory Adobe Commerce, Commerce B2B, and Magento Open Source editions and exact patch levels.
Compare each deployment against APSB26-49 affected and corrected release information.
Confirm production nodes and immutable images use the intended updated dependency set.
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-1395: 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-1395 · source CWE mapping
Dependency on Vulnerable Third-Party Component
Dependency on Vulnerable Third-Party Component represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.