CVE-2026-2053

published 26 Jun 2026 · updated 26 Jun 2026

Unauthenticated Server-Side Request Forgery via WS-Addressing in WSO2 API Manager

8.3HighCVSS 8.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in API Manager 3.1.0.360, API Manager 3.2.0.465, API Manager 3.2.1.84 and 2 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
WSO2API Manager>=3.1.0 <3.1.0.360, >=3.2.0 <3.2.0.465, >=3.2.1 <3.2.1.84, >=4.0.0 <4.0.0.385, >=4.2.0 <4.2.0.1893.1.0.360, 3.2.0.465, 3.2.1.84, 4.0.0.385, 4.2.0.189

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in WSO2, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-2053 severity on Zeptric[![CVE-2026-2053](https://zeptric.io/badge/cve/CVE-2026-2053.svg)](https://zeptric.io/cve/CVE-2026-2053)