CVE-2025-15039: The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of a

This month

CRITICAL 9.4REMOTEUPGRADEUPGRADEUPGRADE

CVE-2025-15039 is a critical-severity flaw (CVSS 9.4) affecting api control plane, api manager, identity server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of all required authentication steps when a specific multi-step pattern involving certain authenticators is configured. This allows an attacker to bypass intermediate authentication challenges by exploiting how the script handles callbacks and re-execution of authentication steps. Successful exploitation allows a malicious actor to gain unau

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.4 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 48%)
CISA exploited list	No
Weakness	CWE-693
Published	2026-08-06
Last modified	2026-09-29

Publisher (CNA): WSO2 LLC · Vendor: wso2

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

Am I affected?

Timeline

2026-08-06 08:16 UTCPublished CVE record published
2026-09-29 14:10 UTCUpdated Record last modified

wso2 api control plane UPGRADE

Affected: >= 4.5.0 and < 4.5.0.45 · >= 4.6.0 and < 4.6.0.9

Fixed in: 4.5.0.45, 4.6.0.9

Safe to downgrade to: a release before 4.5.0

1. Check installed version

apt-cache policy api-control-plane || rpm -q api-control-plane || api-control-plane --version

2. UPGRADE to 4.5.0.45 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade api-control-plane

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade api-control-plane

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 4.5.0 (Debian / Ubuntu)

apt-cache madison api-control-plane sudo apt install api-control-plane=<VERSION_BEFORE_4.5.0> sudo apt-mark hold api-control-plane

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

dnf --showduplicates list api-control-plane sudo dnf downgrade api-control-plane-<VERSION_BEFORE_4.5.0> sudo dnf versionlock add api-control-plane

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.

wso2 api manager UPGRADE

Affected: >= 2.6.0 and < 2.6.0.150 · >= 3.0.0 and < 3.0.0.180 · >= 3.1.0 and < 3.1.0.356 · >= 3.2.0 and < 3.2.0.460 · >= 3.2.1 and < 3.2.1.79 · >= 4.0.0 and < 4.0.0.381 · >= 4.1.0 and < 4.1.0.244 · >= 4.2.0 and < 4.2.0.184

Fixed in: 2.6.0.150, 3.0.0.180, 3.1.0.356, 3.2.0.460, 3.2.1.79, 4.0.0.381, 4.1.0.244, 4.2.0.184, 4.3.0.95, 4.4.0.59, 4.5.0.44, 4.6.0.8

Safe to downgrade to: a release before 2.6.0

1. Check installed version

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

2. UPGRADE to 2.6.0.150 (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 2.6.0 (Debian / Ubuntu)

apt-cache madison api-manager sudo apt install api-manager=<VERSION_BEFORE_2.6.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_2.6.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.

wso2 identity server UPGRADE

Affected: >= 5.7.0 and < 5.7.0.130 · >= 5.8.0 and < 5.8.0.133 · >= 5.9.0 and < 5.9.0.173 · >= 5.10.0 and < 5.10.0.385 · >= 5.11.0 and < 5.11.0.432 · >= 6.0.0 and < 6.0.0.259 · >= 6.1.0 and < 6.1.0.260 · >= 7.0.0 and < 7.0.0.138

Fixed in: 5.7.0.130, 5.8.0.133, 5.9.0.173, 5.10.0.385, 5.11.0.432, 6.0.0.259, 6.1.0.260, 7.0.0.138, 7.1.0.49, 7.2.0.7

Safe to downgrade to: a release before 5.7.0

1. Check installed version

apt-cache policy identity-server || rpm -q identity-server || identity-server --version

2. UPGRADE to 5.7.0.130 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade identity-server

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade identity-server

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 5.7.0 (Debian / Ubuntu)

apt-cache madison identity-server sudo apt install identity-server=<VERSION_BEFORE_5.7.0> sudo apt-mark hold identity-server

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

dnf --showduplicates list identity-server sudo dnf downgrade identity-server-<VERSION_BEFORE_5.7.0> sudo dnf versionlock add identity-server

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.

wso2 identity server as key manager UPGRADE

Affected: >= 5.7.0 and < 5.7.0.129 · >= 5.9.0 and < 5.9.0.179 · >= 5.10.0 and < 5.10.0.376

Fixed in: 5.7.0.129, 5.9.0.179, 5.10.0.376

Safe to downgrade to: a release before 5.7.0

1. Check installed version

apt-cache policy identity-server-as-key-manager || rpm -q identity-server-as-key-manager || identity-server-as-key-manager --version

2. UPGRADE to 5.7.0.129 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade identity-server-as-key-manager

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade identity-server-as-key-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 5.7.0 (Debian / Ubuntu)

apt-cache madison identity-server-as-key-manager sudo apt install identity-server-as-key-manager=<VERSION_BEFORE_5.7.0> sudo apt-mark hold identity-server-as-key-manager

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

dnf --showduplicates list identity-server-as-key-manager sudo dnf downgrade identity-server-as-key-manager-<VERSION_BEFORE_5.7.0> sudo dnf versionlock add identity-server-as-key-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.

wso2 open banking am UPGRADE

Affected: >= 1.4.0 and < 1.4.0.143 · >= 1.5.0 and < 1.5.0.144 · >= 2.0.0 and < 2.0.0.405

Fixed in: 1.4.0.143, 1.5.0.144, 2.0.0.405

Safe to downgrade to: a release before 1.4.0

1. Check installed version

apt-cache policy open-banking-am || rpm -q open-banking-am || open-banking-am --version

2. UPGRADE to 1.4.0.143 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade open-banking-am

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade open-banking-am

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 1.4.0 (Debian / Ubuntu)

apt-cache madison open-banking-am sudo apt install open-banking-am=<VERSION_BEFORE_1.4.0> sudo apt-mark hold open-banking-am

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

dnf --showduplicates list open-banking-am sudo dnf downgrade open-banking-am-<VERSION_BEFORE_1.4.0> sudo dnf versionlock add open-banking-am

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.

wso2 open banking iam UPGRADE

Affected: >= 2.0.0 and < 2.0.0.425

Fixed in: 2.0.0.425

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy open-banking-iam || rpm -q open-banking-iam || open-banking-iam --version

2. UPGRADE to 2.0.0.425 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade open-banking-iam

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade open-banking-iam

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 2.0.0 (Debian / Ubuntu)

apt-cache madison open-banking-iam sudo apt install open-banking-iam=<VERSION_BEFORE_2.0.0> sudo apt-mark hold open-banking-iam

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

dnf --showduplicates list open-banking-iam sudo dnf downgrade open-banking-iam-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add open-banking-iam

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-2025-15039?

api control plane: upgrade to 4.5.0.45, 4.6.0.9; api manager: upgrade to 2.6.0.150, 3.0.0.180, 3.1.0.356, 3.2.0.460, 3.2.1.79, 4.0.0.381, 4.1.0.244, 4.2.0.184, 4.3.0.95, 4.4.0.59, 4.5.0.44, 4.6.0.8; identity server: upgrade to 5.7.0.130, 5.8.0.133, 5.9.0.173, 5.10.0.385, 5.11.0.432, 6.0.0.259, 6.1.0.260, 7.0.0.138, 7.1.0.49, 7.2.0.7. Exact commands for each OS are on this page.

Is CVE-2025-15039 being exploited?

CVE-2025-15039 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-2025-15039 affect?

CVE-2025-15039 affects api control plane, api manager, identity server. Severity is critical (CVSS 9.4). The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of all required authentication steps when a specific multi-step pattern involving certain authenticators is configured. This allows an

How urgent is CVE-2025-15039?

Priority 51/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-12737 HIGH 8.4 UPGRADE UPGRADE The administrative operations within the Carbon Console do not adequately validate specific user-supplied inpu
CVE-2025-13394 MEDIUM 5.4 UPGRADE UPGRADE The Ajax processor within the Carbon console fails to adequately protect state-changing operations from Cross-
CVE-2026-5430 CRITICAL 10.0 EXPLOITED UPGRADE UPGRADE WSO2 Multiple Products Path Traversal Vulnerability
CVE-2026-3416 MEDIUM 5.9 UPGRADE UPGRADE The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create
CVE-2026-2445 MEDIUM 6.1 UPGRADE UPGRADE The affected product accepts user-supplied input within a URL parameter without enforcing expected sanitizatio

References

← Back to latest CVEs