CVE-2026-2053Network attack vector

Unauthenticated SSRF via attacker-controlled WS-Addressing destination

Published Jun 26, 2026 · Updated Jun 26, 2026

SSRF in WSO2 API Manager allows remote attackers to reach internal services through crafted WS-Addressing headers. The message flow component accepts an attacker-controlled wsa:To destination and initiates a server-side request without adequately validating or restricting that address. Exploitation is unauthenticated and depends on deployments where global Synapse handlers build the message before the main mediation sequence, exposing resources reachable from the API Manager host.

CVSS severity8.3
High
EPSS probability0.39%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

SSRF in WSO2 API Manager allows remote attackers to reach internal services through crafted WS-Addressing headers. The message flow component accepts an attacker-controlled wsa:To destination and initiates a server-side request without adequately validating or restricting that address. Exploitation is unauthenticated and depends on deployments where global Synapse handlers build the message before the main mediation sequence, exposing resources reachable from the API Manager host.

The record

CVE
CVE-2026-2053
Published
Jun 26, 2026
Updated
Jun 26, 2026
Vendor
WSO2
Product
WSO2 API Manager
Classifications
CWE-918, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 26, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 26, 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.

  1. Affected versionversion=3.1.0 <3.1.0.360
  2. Affected versionversion=3.2.0 <3.2.0.465
  3. Affected versionversion=3.2.1 <3.2.1.84
  4. Affected versionversion=4.0.0 <4.0.0.385
  5. Affected versionversion=4.2.0 <4.2.0.189

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

WSO2 · WSO2 API Managerversion=3.1.0 <3.1.0.360; version=3.2.0 <3.2.0.465; version=3.2.1 <3.2.1.84; version=4.0.0 <4.0.0.385; version=4.2.0 <4.2.0.189

Published CVSS scores

10.0NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
8.3WSO2 LLCCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
T1190Exploit Public-Facing Application

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