CVE-2026-2053: The WSO2 API Manager's message flow component, when processing WS-Addressing headers, does not sufficiently va

This month

HIGH 8.3REMOTEUPGRADE

CVE-2026-2053 is a high-severity flaw (CVSS 8.3) affecting api manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 A

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 67%)
CISA exploited list	No
Weakness	CWE-918
Published	2026-06-26
Last modified	2026-10-25

Publisher (CNA): WSO2 LLC · Vendor: wso2

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-26 08:16 UTCPublished CVE record published
2026-10-25 22:10 UTCUpdated Record last modified

wso2 api manager UPGRADE

Affected: >= 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

Fixed in: 3.1.0.360, 3.2.0.465, 3.2.1.84, 4.0.0.385, 4.2.0.189

Safe to downgrade to: a release before 3.1.0

1. Check installed version

apt-cache policy api-manager || rpm -q api-manager || api-manager --version

2. UPGRADE to 3.1.0.360 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade api-manager

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade api-manager

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.1.0 (Debian / Ubuntu)

apt-cache madison api-manager sudo apt install api-manager=<VERSION_BEFORE_3.1.0> sudo apt-mark hold api-manager

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list api-manager sudo dnf downgrade api-manager-<VERSION_BEFORE_3.1.0> sudo dnf versionlock add api-manager

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-2053?

api manager: upgrade to 3.1.0.360, 3.2.0.465, 3.2.1.84, 4.0.0.385, 4.2.0.189. Exact commands for each OS are on this page.

Is CVE-2026-2053 being exploited?

CVE-2026-2053 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-2053 affect?

CVE-2026-2053 affects api manager. Severity is high (CVSS 8.3). 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 header

How urgent is CVE-2026-2053?

Priority 42/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-5430 CRITICAL 10.0 EXPLOITED UPGRADE UPGRADE WSO2 Multiple Products Path Traversal Vulnerability

References

← Back to latest CVEs