CVE-2026-2053: CWE-918 Server-Side Request Forgery (SSRF) in WSO2 WSO2 API Manager
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.
AI Analysis
Technical Summary
The WSO2 API Manager's message flow component does not properly validate or restrict user input in WS-Addressing headers. This allows an unauthenticated attacker to control the destination of server-initiated requests, potentially accessing internal services or resources that are normally inaccessible externally. The vulnerability is classified as CWE-918 (Server-Side Request Forgery). Affected versions include 3.1.0, 3.2.0, 3.2.1, 4.0.0, and 4.2.0. There is no vendor advisory indicating an available patch or mitigation at this time.
Potential Impact
Successful exploitation allows an unauthenticated attacker to specify arbitrary destinations for server-initiated requests, potentially leading to unauthorized access to internal network resources or services. This can result in confidentiality, integrity, and availability impacts as indicated by the CVSS vector (C:L/I:L/A:L).
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider restricting access to the affected WS-Addressing functionality or apply network-level controls to limit server-initiated request destinations if possible.
CVE-2026-2053: CWE-918 Server-Side Request Forgery (SSRF) in WSO2 WSO2 API Manager
Description
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.
CVSS v3.1
Score 8.3high
Affected software
pkg:maven/org.wso2/wso2-api-managerRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The WSO2 API Manager's message flow component does not properly validate or restrict user input in WS-Addressing headers. This allows an unauthenticated attacker to control the destination of server-initiated requests, potentially accessing internal services or resources that are normally inaccessible externally. The vulnerability is classified as CWE-918 (Server-Side Request Forgery). Affected versions include 3.1.0, 3.2.0, 3.2.1, 4.0.0, and 4.2.0. There is no vendor advisory indicating an available patch or mitigation at this time.
Potential Impact
Successful exploitation allows an unauthenticated attacker to specify arbitrary destinations for server-initiated requests, potentially leading to unauthorized access to internal network resources or services. This can result in confidentiality, integrity, and availability impacts as indicated by the CVSS vector (C:L/I:L/A:L).
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider restricting access to the affected WS-Addressing functionality or apply network-level controls to limit server-initiated request destinations if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- WSO2
- Date Reserved
- 2026-02-06T06:12:48.334Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3e2e3e4853345fc17628c6
Added to database: 06/26/2026, 07:46:06 UTC
Last enriched: 06/26/2026, 08:02:04 UTC
Last updated: 08/10/2026, 12:41:10 UTC
Views: 99
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.