Is CVE-2026-2053 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-2053 being exploited in the wild.

How severe is CVE-2026-2053?

High severity, with a CVSS score of 8.3, published 26 June 2026.

Which products and versions are affected?

Wso2 API Manager 3.1.0 before update 360, 3.2.0 before update 465, 3.2.1 before update 84, 4.0.0 before update 385, 4.2.0 before update 189.

Is there a fix for CVE-2026-2053?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-2053 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-2053?

Check whether you run Wso2 API Manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-2053: WSO2 API Manager SSRF in WS-Addressing headers

CVE-2026-2053 · Severity: high · CVSS 8.3 · Published 2026-06-26

WSO2 API Manager is a platform used by organizations to create, manage, and secure digital interfaces (APIs). A security flaw in how the system handles certain message headers allows an attacker to force the server to make unauthorized requests to internal systems. This could allow an outsider to bypass firewall protections and access sensitive internal data or services that are not intended to be public.

Technologies: Wso2 API Manager. Vendors: Wso2.

Quick answers

Is CVE-2026-2053 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-2053 being exploited in the wild.
How severe is CVE-2026-2053?: High severity, with a CVSS score of 8.3, published 26 June 2026.
Which products and versions are affected?: Wso2 API Manager 3.1.0 before update 360, 3.2.0 before update 465, 3.2.1 before update 84, 4.0.0 before update 385, 4.2.0 before update 189.
Is there a fix for CVE-2026-2053?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-2053 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-2053?: Check whether you run Wso2 API Manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in the WSO2 API Manager message flow component due to insufficient validation of WS-Addressing headers. In specific configurations where custom handlers or global Synapse handlers trigger message building early in the mediation sequence, the system processes user-controlled WS-Addressing headers to determine outbound request destinations. An unauthenticated remote attacker can exploit this by supplying crafted header values to redirect server-initiated requests toward internal network resources. The vulnerability affects versions 3.1.0 through 4.2.0; fixes are available via specific update levels for each version or by migrating to the latest unaffected release.

Affected products

WSO2 API Manager 3.1.0 before update 360, 3.2.0 before update 465, 3.2.1 before update 84, 4.0.0 before update 385, 4.2.0 before update 189

Timeline

2026-05-03: advisory: Initial advisory published by WSO2
2026-06-26: disclosed: CVE published to NVD dataset

References

https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5072/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.