Application crash via vulnerable third-party dependency
Published May 12, 2026 · Updated May 12, 2026
Dependency-based denial of service in Adobe Commerce 2.4.9-beta1 and earlier release lines allows attackers to crash the application remotely. Adobe identifies a vulnerable third-party component but does not disclose the dependency, affected code path, or unsafe operation that triggers the crash. Adobe's authentication column says credentials are required, while its published PR:N vector says none are required; neither user interaction nor administrator rights is needed.
Summary
What happened
Dependency-based denial of service in Adobe Commerce 2.4.9-beta1 and earlier release lines allows attackers to crash the application remotely. Adobe identifies a vulnerable third-party component but does not disclose the dependency, affected code path, or unsafe operation that triggers the crash. Adobe's authentication column says credentials are required, while its published PR:N vector says none are required; neither user interaction nor administrator rights is needed.
The record
- CVE
- CVE-2026-34654
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- Adobe
- Product
- Adobe Commerce
- Classifications
- CWE-1395, T1499
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- May 12, 2026CVE publishedPublication date reported by the CVE source.
- May 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.4.4-p17
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo