Answer in brief
CVE-2024-9517 records a Medium severity (CVSS 4.9) vulnerability in Improper Token Renewal in Refresh Token Grant in Multiple WSO2 Products Allows Unauthorized Access to Blocked Accounts. 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 4.9. 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.10 | 4.5.0.10 |
| WSO2/WSO2 API Managergeneric | >=3.1.0 <3.1.0.308 || >=3.2.0 <3.2.0.429 || >=3.2.1 <3.2.1.49 || >=4.0.0 <4.0.0.315 || >=4.1.0 <4.1.0.214 || >=4.2.0 <4.2.0.149 || >=4.3.0 <4.3.0.62 || >=4.4.0 <4.4.0.25 || >=4.5.0 <4.5.0.9 | 3.1.0.308, 3.2.0.429, 3.2.1.49, 4.0.0.315, 4.1.0.214, 4.2.0.149, 4.3.0.62, 4.4.0.25, 4.5.0.9 |
| WSO2/WSO2 Carbon OAuthgeneric | >=6.4.2 <6.4.2.148 || >=6.4.111 <6.4.111.122 || >=6.4.176 <6.4.176.26 || >=6.4.180 <6.4.180.10 || >=6.8.0 <6.8.0.44 || >=6.9.6 <6.9.6.21 || >=6.11.21 <6.11.21.64 || >=6.13.16 <6.13.16.13 || >=6.13.19 <6.13.19.7 || >=6.13.27 <6.13.27.1 || >=7.0.26 <7.0.26.37 | 6.4.2.148, 6.4.111.122, 6.4.176.26, 6.4.180.10, 6.8.0.44, 6.9.6.21, 6.11.21.64, 6.13.16.13, 6.13.19.7, 6.13.27.1, 7.0.26.37 |
| WSO2/WSO2 Identity Servergeneric | >=5.10.0 <5.10.0.331 || >=5.11.0 <5.11.0.376 || >=6.0.0 <6.0.0.219 || >=6.1.0 <6.1.0.205 || >=7.0.0 <7.0.0.73 | 5.10.0.331, 5.11.0.376, 6.0.0.219, 6.1.0.205, 7.0.0.73 |
| WSO2/WSO2 Identity Server as Key Managergeneric | >=5.10.0 <5.10.0.324 | 5.10.0.324 |
| WSO2/WSO2 Open Banking AMgeneric | >=2.0.0 <2.0.0.357 | 2.0.0.357 |
| WSO2/WSO2 Open Banking IAMgeneric | >=2.0.0 <2.0.0.377 | 2.0.0.377 |
| WSO2/WSO2 Traffic Managergeneric | >=4.5.0 <4.5.0.9 | 4.5.0.9 |
| WSO2/WSO2 Universal Gatewaygeneric | >=4.5.0 <4.5.0.9 | 4.5.0.9 |
Published upstream
Nov 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 2, 2026
The refresh token grant type in WSO2 products fails to re-validate account status before issuing new access tokens. This weakness allows an attacker to obtain valid access tokens for user accounts even after they have been blocked by the user store, bypassing account lockout mechanisms. This vulnerability can lead to unauthorized access to user accounts and their associated resources. Attackers can leverage this to perform actions on behalf of blocked users, potentially leading to privilege escalation or data exfiltration depending on the permissions of the compromised account.
Quoted source text, attributed separately from HOL analysis.