CVE-2026-2053: Unauthenticated Server-Side Request Forgery via WS-Addressing in WSO2 API Manager

Published Jun 26, 2026
·
Updated

The WSO2 API Manager's message flow component, when processing WS-Addressing headers, does not sufficiently validate or restrict user-controlled input within these headers. This omission allows an attacker to manipulate WS-Addressing headers to specify arbitrary destinations for server-initiated requests.

Successful exploitation allows an unauthenticated attacker to control the destination of server-initiated requests originating from the WSO2 API Manager. This direct control can enable unauthorized access to internal network resources or services that would typically be inaccessible from external networks.

Affected Software

6 affected components
WSO2 WSO2 API Manager
WSO2 API Manager>=3.1.0<3.1.0.360
WSO2 API Manager>=3.2.0<3.2.0.465
WSO2 API Manager>=3.2.1<3.2.1.84
WSO2 API Manager>=4.0.0<4.0.0.385
WSO2 API Manager>=4.2.0<4.2.0.189

Event History

Jun 26, 2026
CVE Published
via MITRE·07:26 AM
Data Sourced
via MITRE·07:26 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·08:16 AM
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-2053?

CVE-2026-2053 has a critical severity rating of 10.

2

What does CVE-2026-2053 exploit?

CVE-2026-2053 exploits a vulnerability in the WSO2 API Manager's handling of WS-Addressing headers, allowing unauthenticated server-side request forgery (SSRF).

3

How does CVE-2026-2053 affect WSO2 API Manager?

CVE-2026-2053 allows attackers to manipulate WS-Addressing headers to direct server-initiated requests to arbitrary destinations.

4

How do I fix CVE-2026-2053?

To fix CVE-2026-2053, update to the patched version of WSO2 API Manager provided by WSO2 in their security announcements.

5

When was CVE-2026-2053 published?

CVE-2026-2053 was published on June 26, 2026.

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