Improper IDP Status Validation via JWT Bearer or SAML2 Bearer Grants in Multiple WSO2 Products Allows Access Token Issuance for Disabled Identity Providers

Description

When utilizing JWT Bearer or SAML2 Bearer grant types, the system fails to validate the status of the Identity Provider (IDP) before issuing access tokens. This oversight permits tokens to be generated even when the associated IDP has been disabled. A malicious actor could leverage this vulnerability to obtain access tokens by targeting a disabled IDP. This could enable them to bypass intended security controls and potentially access protected resources that should be inaccessible due to the IDP's disabled state.

Scores

EPSS (exploitation in 30 days)

0.15% · top 96% of all CVEs (6 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.8.

Weakness

• CWE-862: Missing Authentication for Critical Function (opens in a new tab)All about CWE-862 and its CVEs

Affected products

• WSO2 · WSO2 Universal Gateway

  • affected 4.5.0 – < 4.5.0.10

• WSO2 · WSO2 Traffic Manager

  • affected 4.5.0 – < 4.5.0.10

• WSO2 · WSO2 API Manager

  • unknown < 3.1.0
  • affected 3.1.0 – < 3.1.0.321
  • affected 3.2.0 – < 3.2.0.414
  • affected 3.2.1 – < 3.2.1.50
  • affected 4.0.0 – < 4.0.0.335
  • affected 4.1.0 – < 4.1.0.211
  • affected 4.2.0 – < 4.2.0.150
  • affected 4.3.0 – < 4.3.0.63
  • affected 4.4.0 – < 4.4.0.26
  • affected 4.5.0 – < 4.5.0.10

• WSO2 · WSO2 API Control Plane

  • affected 4.5.0 – < 4.5.0.11

• WSO2 · WSO2 Identity Server

  • unknown < 5.10.0
  • affected 5.10.0 – < 5.10.0.346
  • affected 5.11.0 – < 5.11.0.396
  • affected 6.0.0 – < 6.0.0.232
  • affected 6.1.0 – < 6.1.0.224
  • affected 7.0.0 – < 7.0.0.93

• WSO2 · WSO2 Open Banking AM

  • unknown < 2.0.0
  • affected 2.0.0 – < 2.0.0.370

• WSO2 · WSO2 Open Banking IAM

  • unknown < 2.0.0
  • affected 2.0.0 – < 2.0.0.390

• WSO2 · WSO2 Identity Server as Key Manager

  • unknown < 5.10.0
  • affected 5.10.0 – < 5.10.0.339

• WSO2 · WSO2 Carbon OAuth

  • affected 6.4.2 – < 6.4.2.155
  • affected 6.4.111 – < 6.4.111.134
  • affected 6.4.176 – < 6.4.176.25
  • affected 6.4.180 – < 6.4.180.11
  • affected 6.8.0 – < 6.8.0.49
  • affected 6.9.6 – < 6.9.6.22
  • affected 6.11.21 – < 6.11.21.75
  • affected 6.13.16 – < 6.13.16.15
  • affected 6.13.19 – < 6.13.19.9
  • affected 6.13.27 – < 6.13.27.2
  • affected 7.0.26 – < 7.0.26.58

• WSO2 · JWT Grant Type For OAuth2

  • affected 1.0.26 – < 1.0.26.6
  • affected 1.0.26 – < 1.0.26.7
  • affected 1.0.31 – < 1.0.31.3
  • affected 1.1.0 – < 1.1.0.2
  • affected 2.0.4 – < 2.0.4.3
  • affected 2.1.1 – < 2.1.1.2
  • affected 2.2.0 – < 2.2.0.3
  • affected 2.2.4 – < 2.2.4.1
  • affected 2.3.1 – < 2.3.1.4

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4010/#solution

References (1)

• https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4010/ (opens in a new tab)vendor-advisory

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2025-1397](https://trackcve.app/badge/CVE-2025-1397.svg)](https://trackcve.app/cve/CVE-2025-1397)

Record last updated 3 Nov 2026, 20:03 UTC.