CVE-2025-1397
Improper IDP Status Validation via JWT Bearer or SAML2 Bearer Grants in Multiple WSO2 Products Allows Access Token Issuance for Disabled Identity Providers
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.
Fixes and workarounds
Fix
Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4010/#solution
Source: CNA: WSO2Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| WSO2 Universal Gateway WSO2 |
≥ 4.5.0; < 4.5.0.10 (affected, custom)
Other versions: unaffected |
CNA: WSO2 |
| WSO2 Traffic Manager WSO2 |
≥ 4.5.0; < 4.5.0.10 (affected, custom)
Other versions: unaffected |
CNA: WSO2 |
| WSO2 API Manager WSO2 |
≥ 0; < 3.1.0 (unknown, custom) ≥ 3.1.0; < 3.1.0.321 (affected, custom) ≥ 3.2.0; < 3.2.0.414 (affected, custom) ≥ 3.2.1; < 3.2.1.50 (affected, custom) ≥ 4.0.0; < 4.0.0.335 (affected, custom) ≥ 4.1.0; < 4.1.0.211 (affected, custom) ≥ 4.2.0; < 4.2.0.150 (affected, custom) ≥ 4.3.0; < 4.3.0.63 (affected, custom) ≥ 4.4.0; < 4.4.0.26 (affected, custom) ≥ 4.5.0; < 4.5.0.10 (affected, custom) Other versions: unaffected |
CNA: WSO2 |
| WSO2 API Control Plane WSO2 |
≥ 4.5.0; < 4.5.0.11 (affected, custom)
Other versions: unaffected |
CNA: WSO2 |
| WSO2 Identity Server WSO2 |
≥ 0; < 5.10.0 (unknown, custom) ≥ 5.10.0; < 5.10.0.346 (affected, custom) ≥ 5.11.0; < 5.11.0.396 (affected, custom) ≥ 6.0.0; < 6.0.0.232 (affected, custom) ≥ 6.1.0; < 6.1.0.224 (affected, custom) ≥ 7.0.0; < 7.0.0.93 (affected, custom) Other versions: unaffected |
CNA: WSO2 |
| WSO2 Open Banking AM WSO2 |
≥ 0; < 2.0.0 (unknown, custom) ≥ 2.0.0; < 2.0.0.370 (affected, custom) Other versions: unaffected |
CNA: WSO2 |
| WSO2 Open Banking IAM WSO2 |
≥ 0; < 2.0.0 (unknown, custom) ≥ 2.0.0; < 2.0.0.390 (affected, custom) Other versions: unaffected |
CNA: WSO2 |
| WSO2 Identity Server as Key Manager WSO2 |
≥ 0; < 5.10.0 (unknown, custom) ≥ 5.10.0; < 5.10.0.339 (affected, custom) Other versions: unaffected |
CNA: WSO2 |
| WSO2 Carbon OAuth WSO2 org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth
|
≥ 6.4.2; < 6.4.2.155 (affected, custom) ≥ 6.4.111; < 6.4.111.134 (affected, custom) ≥ 6.4.176; < 6.4.176.25 (affected, custom) ≥ 6.4.180; < 6.4.180.11 (affected, custom) ≥ 6.8.0; < 6.8.0.49 (affected, custom) ≥ 6.9.6; < 6.9.6.22 (affected, custom) ≥ 6.11.21; < 6.11.21.75 (affected, custom) ≥ 6.13.16; < 6.13.16.15 (affected, custom) ≥ 6.13.19; < 6.13.19.9 (affected, custom) ≥ 6.13.27; < 6.13.27.2 (affected, custom) ≥ 7.0.26; < 7.0.26.58 (affected, custom) Other versions: unknown |
CNA: WSO2 |
| JWT Grant Type For OAuth2 WSO2 org.wso2.carbon.extension.identity.oauth2.grantType.jwt:org.wso2.carbon.identity.oauth2.grant.jwt
|
≥ 1.0.26; < 1.0.26.6 (affected, custom) ≥ 1.0.26; < 1.0.26.7 (affected, custom) ≥ 1.0.31; < 1.0.31.3 (affected, custom) ≥ 1.1.0; < 1.1.0.2 (affected, custom) ≥ 2.0.4; < 2.0.4.3 (affected, custom) ≥ 2.1.1; < 2.1.1.2 (affected, custom) ≥ 2.2.0; < 2.2.0.3 (affected, custom) ≥ 2.2.4; < 2.2.4.1 (affected, custom) ≥ 2.3.1; < 2.3.1.4 (affected, custom) Other versions: unknown |
CNA: WSO2 |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 4.8 medium |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | CNA: WSO2 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4010/CNA: WSO2 · vendor-advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.