Critical SSRF

CVE-2026-2053 — WSO2 API Manager SSRF via WS-Addressing Headers in Message Flow

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.

Published Jun 26, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: WSO2

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.4% (30-day exploitation probability)+5
Technical severity (critical)+10
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.39%

ahead of 32% of scored CVEs · Oct 14, 2026

Affects

WSO2

Api Manager

CVSS base

10.0

Critical · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Manager).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (ssrf), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
WSO2	Api Manager	≥ 3.1.0 and < 3.1.0.360≥ 3.2.0 and < 3.2.0.465≥ 3.2.1 and < 3.2.1.84≥ 4.0.0 and < 4.0.0.385≥ 4.2.0 and < 4.2.0.189	Vulnerable	NIST National Vulnerability Database
WSO2	Api Manager	≥ 3.1.0 and < 3.1.0.360≥ 3.2.0 and < 3.2.0.465≥ 3.2.1 and < 3.2.1.84≥ 4.0.0 and < 4.0.0.385≥ 4.2.0 and < 4.2.0.189	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
10.0	CVSS 3.1	Critical	3.9	6.0	nvd@nist.gov via NIST National Vulnerability Database
8.3	CVSS 3.1	High	3.9	3.7	ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database
8.3	CVSS 3.1	High	—	—	WSO2 via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 10.0 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-918 · Server-Side Request Forgery (SSRF)

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.39%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Monitor outbound requests from the server to internal IPs and cloud metadata endpoints.

web/proxy/WAF logsnetwork IDS/IPSegress traffic

Analysis and videos

CVE-2026-2053: WSO2 API Manager SSRF via WS-Addressing Headers in Message Flow
CVE-2026-2053 affects the message flow component of WSO2 API Manager, which does not sufficiently validate user-controlled input in WS-Addressing headers, enabling Server-Side Request Forgery (CWE-918). The NVD assigns a CVSS 3.1 base score of 10.0 (Critical) with network attack vector and no privileges or user interaction required. Defenders should identify deployments within the listed affected ranges, consult the vendor advisory for fixed builds, and restrict outbound traffic from API Manager hosts to internal resources.

Timeline

What happened to this CVE, newest first.

2026
Affected products added · wso2/wso2 api manager
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 10.0
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Jun 26, 2026 · WSO2

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5
Vendor Advisory, vendor-advisory, NIST National Vulnerability Database

Elsewhere on this site

WSO2
every CVE for this vendor

SSRF
same class

CWE-918
other pages naming this weakness

Related CVEs (same products)

High CVE-2025-12737 OS Command Injection in WSO2 Api Control Plane Sep 3, 2026
High CVE-2026-3416 Use of Insufficiently Random Values in WSO2 Api Control Plane Sep 3, 2026
Critical CVE-2026-3418 Arbitrary File Upload via System REST API in Multiple WSO2 Products Allows Remote Code Execution Aug 6, 2026
High CVE-2026-3415 XML External Entity (XXE) Injection via Schema Validation in Multiple WSO2 Products Allows File Reading and Denial of Service Aug 6, 2026
Critical CVE-2025-14561 Access Control Bypass via Publisher REST APIs in Multiple WSO2 Products Allows Cross-Tenant Operations Aug 6, 2026
Medium CVE-2024-6541 Information Disclosure and Integrity Violation via Improper Message Context Handling in Multiple WSO2 Products Aug 6, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-2053 is "WSO2 API Manager SSRF via WS-Addressing Headers in Message Flow", rated Critical. It affects Api Manager (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 10.0 describes technical severity. EPSS 0.39% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.