Answer in brief
CVE-2025-13173 records a Medium severity (CVSS 6.5) vulnerability in Improper Token Revocation via Session-Bound Token Flow in Multiple WSO2 Products Allows Unauthorized Access After Session Termination. The current sources do not mark it as known exploited. The current feed maps WSO2/WSO2 API Control Plane (generic), WSO2/WSO2 API Manager (generic), WSO2/WSO2 Carbon OAuth (generic), WSO2/WSO2 Identity Server (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps WSO2/WSO2 API Control Plane (generic), WSO2/WSO2 API Manager (generic), WSO2/WSO2 Carbon OAuth (generic), WSO2/WSO2 Identity Server (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| WSO2/WSO2 API Control Planegeneric | >=4.5.0 <4.5.0.47 || >=4.6.0 <4.6.0.13 | 4.5.0.47, 4.6.0.13 |
| WSO2/WSO2 API Managergeneric | >=3.1.0 <3.1.0.352 || >=3.2.0 <3.2.0.456 || >=3.2.1 <3.2.1.81 || >=4.0.0 <4.0.0.376 || >=4.1.0 <4.1.0.246 || >=4.2.0 <4.2.0.186 || >=4.3.0 <4.3.0.97 || >=4.4.0 <4.4.0.61 || >=4.5.0 <4.5.0.46 || >=4.6.0 <4.6.0.11 | 3.1.0.352, 3.2.0.456, 3.2.1.81, 4.0.0.376, 4.1.0.246, 4.2.0.186, 4.3.0.97, 4.4.0.61, 4.5.0.46, 4.6.0.11 |
| WSO2/WSO2 Carbon OAuthgeneric | >=6.4.2 <6.4.2.171 || >=6.4.111 <6.4.111.165 || >=6.4.176 <6.4.176.30 || >=6.4.180 <6.4.180.14 || >=6.8.0 <6.8.0.54 || >=6.9.6 <6.9.6.29 || >=6.11.21 <6.11.21.94 || >=6.13.16 <6.13.16.21 || >=6.13.19 <6.13.19.14 || >=6.13.27 <6.13.27.10 || >=6.13.41 <6.13.41.1 || >=7.0.26 <7.0.26.87 || >=7.0.259 <7.0.259.34 || >=7.0.385 <7.0.385.3 | 6.4.2.171, 6.4.111.165, 6.4.176.30, 6.4.180.14, 6.8.0.54, 6.9.6.29, 6.11.21.94, 6.13.16.21, 6.13.19.14, 6.13.27.10, 6.13.41.1, 7.0.26.87, 7.0.259.34, 7.0.385.3 |
| WSO2/WSO2 Identity Servergeneric | >=5.10.0 <5.10.0.381 || >=5.11.0 <5.11.0.428 || >=6.0.0 <6.0.0.255 || >=6.1.0 <6.1.0.256 || >=7.0.0 <7.0.0.133 || >=7.1.0 <7.1.0.41 || >=7.2.0 <7.2.0.3 | 5.10.0.381, 5.11.0.428, 6.0.0.255, 6.1.0.256, 7.0.0.133, 7.1.0.41, 7.2.0.3 |
| WSO2/WSO2 Identity Server as Key Managergeneric | >=5.10.0 <5.10.0.372 | 5.10.0.372 |
| WSO2/WSO2 Open Banking AMgeneric | >=2.0.0 <2.0.0.401 | 2.0.0.401 |
| WSO2/WSO2 Open Banking IAMgeneric | >=2.0.0 <2.0.0.421 | 2.0.0.421 |
| WSO2/WSO2 Traffic Managergeneric | >=4.5.0 <4.5.0.45 || >=4.6.0 <4.6.0.11 | 4.5.0.45, 4.6.0.11 |
| WSO2/WSO2 Universal Gatewaygeneric | >=4.5.0 <4.5.0.46 || >=4.6.0 <4.6.0.11 | 4.5.0.46, 4.6.0.11 |
Published upstream
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 19, 2026
Tokens associated with user sessions are not revoked when the corresponding user session is terminated, unless another SSO request is initiated. This occurs when the session-bound token feature is enabled with token binding validation and the "Revoke token upon user logout" option is not active. The software fails to automatically invalidate session-bound tokens upon user session termination. This vulnerability exists when token binding validation is enabled. As a result, a malicious actor possessing a valid session-bound token could exploit this condition to maintain unauthorized access to applications and resources even after the associated user session has ended, potentially leading to the exposure of sensitive user data.
Quoted source text, attributed separately from HOL analysis.