CVE-2026-34647: Adobe Commerce | Server-Side Request Forgery (SSRF) (CWE-918)

Published May 12, 2026
·
Updated

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.

Affected Software

162 affected components
Adobe Adobe Commerce<=2.4.9-beta1
Adobe Commerce<2.4.4
Adobe Commerce=2.4.4
Adobe Commerce=2.4.4-p1
Adobe Commerce=2.4.4-p10
Adobe Commerce=2.4.4-p11
Adobe Commerce=2.4.4-p12
Adobe Commerce=2.4.4-p13
Adobe Commerce=2.4.4-p14
Adobe Commerce=2.4.4-p15
Adobe Commerce=2.4.4-p16
Adobe Commerce=2.4.4-p17
Adobe Commerce=2.4.4-p2
Adobe Commerce=2.4.4-p3
Adobe Commerce=2.4.4-p4
Adobe Commerce=2.4.4-p5
Adobe Commerce=2.4.4-p6
Adobe Commerce=2.4.4-p7
Adobe Commerce=2.4.4-p8
Adobe Commerce=2.4.4-p9
Adobe Commerce=2.4.5
Adobe Commerce=2.4.5-p1
Adobe Commerce=2.4.5-p10
Adobe Commerce=2.4.5-p11
Adobe Commerce=2.4.5-p12
Adobe Commerce=2.4.5-p13
Adobe Commerce=2.4.5-p14
Adobe Commerce=2.4.5-p15
Adobe Commerce=2.4.5-p16
Adobe Commerce=2.4.5-p2
Adobe Commerce=2.4.5-p3
Adobe Commerce=2.4.5-p4
Adobe Commerce=2.4.5-p5
Adobe Commerce=2.4.5-p6
Adobe Commerce=2.4.5-p7
Adobe Commerce=2.4.5-p8
Adobe Commerce=2.4.5-p9
Adobe Commerce=2.4.6
Adobe Commerce=2.4.6-p1
Adobe Commerce=2.4.6-p10
Adobe Commerce=2.4.6-p11
Adobe Commerce=2.4.6-p12
Adobe Commerce=2.4.6-p13
Adobe Commerce=2.4.6-p14
Adobe Commerce=2.4.6-p2
Adobe Commerce=2.4.6-p3
Adobe Commerce=2.4.6-p4
Adobe Commerce=2.4.6-p5
Adobe Commerce=2.4.6-p6
Adobe Commerce=2.4.6-p7
Adobe Commerce=2.4.6-p8
Adobe Commerce=2.4.6-p9
Adobe Commerce=2.4.7
Adobe Commerce=2.4.7-b1
Adobe Commerce=2.4.7-b2
Adobe Commerce=2.4.7-beta3
Adobe Commerce=2.4.7-p1
Adobe Commerce=2.4.7-p2
Adobe Commerce=2.4.7-p3
Adobe Commerce=2.4.7-p4
Adobe Commerce=2.4.7-p5
Adobe Commerce=2.4.7-p6
Adobe Commerce=2.4.7-p7
Adobe Commerce=2.4.7-p8
Adobe Commerce=2.4.7-p9
Adobe Commerce=2.4.8
Adobe Commerce=2.4.8-beta1
Adobe Commerce=2.4.8-beta2
Adobe Commerce=2.4.8-p1
Adobe Commerce=2.4.8-p2
Adobe Commerce=2.4.8-p3
Adobe Commerce=2.4.8-p4
Adobe Commerce=2.4.9-beta1
Adobe Commerce B2b<1.3.3
Adobe Commerce B2b=1.3.3
Adobe Commerce B2b=1.3.3-p1
Adobe Commerce B2b=1.3.3-p10
Adobe Commerce B2b=1.3.3-p11
Adobe Commerce B2b=1.3.3-p12
Adobe Commerce B2b=1.3.3-p13
Adobe Commerce B2b=1.3.3-p14
Adobe Commerce B2b=1.3.3-p15
Adobe Commerce B2b=1.3.3-p16
Adobe Commerce B2b=1.3.3-p17
Adobe Commerce B2b=1.3.3-p2
Adobe Commerce B2b=1.3.3-p3
Adobe Commerce B2b=1.3.3-p4
Adobe Commerce B2b=1.3.3-p5
Adobe Commerce B2b=1.3.3-p6
Adobe Commerce B2b=1.3.3-p7
Adobe Commerce B2b=1.3.3-p8
Adobe Commerce B2b=1.3.3-p9
Adobe Commerce B2b=1.3.4
Adobe Commerce B2b=1.3.4-p1
Adobe Commerce B2b=1.3.4-p10
Adobe Commerce B2b=1.3.4-p11
Adobe Commerce B2b=1.3.4-p12
Adobe Commerce B2b=1.3.4-p13
Adobe Commerce B2b=1.3.4-p14
Adobe Commerce B2b=1.3.4-p15
Adobe Commerce B2b=1.3.4-p16
Adobe Commerce B2b=1.3.4-p2
Adobe Commerce B2b=1.3.4-p3
Adobe Commerce B2b=1.3.4-p4
Adobe Commerce B2b=1.3.4-p5
Adobe Commerce B2b=1.3.4-p6
Adobe Commerce B2b=1.3.4-p7
Adobe Commerce B2b=1.3.4-p8
Adobe Commerce B2b=1.3.4-p9
Adobe Commerce B2b=1.4.2
Adobe Commerce B2b=1.4.2-p1
Adobe Commerce B2b=1.4.2-p2
Adobe Commerce B2b=1.4.2-p3
Adobe Commerce B2b=1.4.2-p4
Adobe Commerce B2b=1.4.2-p5
Adobe Commerce B2b=1.4.2-p6
Adobe Commerce B2b=1.4.2-p7
Adobe Commerce B2b=1.4.2-p8
Adobe Commerce B2b=1.4.2-p9
Adobe Commerce B2b=1.5.2
Adobe Commerce B2b=1.5.2-p1
Adobe Commerce B2b=1.5.2-p2
Adobe Commerce B2b=1.5.2-p3
Adobe Commerce B2b=1.5.2-p4
Adobe Commerce B2b=1.5.3-beta1
Adobe Magento<2.4.6
Adobe Magento=2.4.6
Adobe Magento=2.4.6-p1
Adobe Magento=2.4.6-p10
Adobe Magento=2.4.6-p11
Adobe Magento=2.4.6-p12
Adobe Magento=2.4.6-p13
Adobe Magento=2.4.6-p14
Adobe Magento=2.4.6-p2
Adobe Magento=2.4.6-p3
Adobe Magento=2.4.6-p4
Adobe Magento=2.4.6-p5
Adobe Magento=2.4.6-p6
Adobe Magento=2.4.6-p7
Adobe Magento=2.4.6-p8
Adobe Magento=2.4.6-p9
Adobe Magento=2.4.7
Adobe Magento=2.4.7-b1
Adobe Magento=2.4.7-b2
Adobe Magento=2.4.7-beta3
Adobe Magento=2.4.7-p1
Adobe Magento=2.4.7-p2
Adobe Magento=2.4.7-p3
Adobe Magento=2.4.7-p4
Adobe Magento=2.4.7-p5
Adobe Magento=2.4.7-p6
Adobe Magento=2.4.7-p7
Adobe Magento=2.4.7-p8
Adobe Magento=2.4.7-p9
Adobe Magento=2.4.8
Adobe Magento=2.4.8-beta1
Adobe Magento=2.4.8-beta2
Adobe Magento=2.4.8-p1
Adobe Magento=2.4.8-p2
Adobe Magento=2.4.8-p3
Adobe Magento=2.4.8-p4
Adobe Magento=2.4.9-beta1

Event History

May 12, 2026
CVE Published
via MITRE·07:50 PM
Data Sourced
via MITRE·07:50 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-34647?

CVE-2026-34647 has been rated as a critical severity vulnerability due to its potential for server-side request forgery.

2

How do I fix CVE-2026-34647?

To fix CVE-2026-34647, upgrade Adobe Commerce to the latest version that addresses this SSRF vulnerability.

3

Which versions are affected by CVE-2026-34647?

CVE-2026-34647 affects 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.

4

What type of vulnerability is CVE-2026-34647?

CVE-2026-34647 is classified as a Server-Side Request Forgery (SSRF) vulnerability.

5

What potential impact does CVE-2026-34647 have?

The exploitation of CVE-2026-34647 could lead to a security feature bypass, allowing attackers to manipulate server requests.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203