Improper Token Revocation in WSO2 Identity Server Allows Unauthorized Access
Summary
| CVE | CVE-2025-0326 |
|---|---|
| State | PUBLISHED |
| Assigner | WSO2 |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-21 14:17:06 UTC |
| Updated | 2026-10-21 18:37:59 UTC |
| Description | The system fails to invalidate existing access tokens associated with sub-organization users during sensitive account management operations such as password reset, role change, or sub-organization disablement. This oversight allows previously issued tokens to remain active even after the user's access context has been modified or revoked through administrative actions. The identified issue could lead to unauthorized access by a malicious actor, but only when all of the following conditions are met: previously issued access tokens remain active, and these tokens have been exposed to malicious actors. |
Risk And Classification
Problem Types: CWE-613 | CWE-613 CWE-613: Insufficient Session Expiration
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | WSO2 | WSO2 Identity Server | unknown 7.0.0 custom | Not specified |
| CNA | WSO2 | WSO2 Identity Server | affected 7.0.0 7.0.0.85 custom | Not specified |
| CNA | WSO2 | WSO2 Carbon OAuth | affected 7.0.26 7.0.26.51 custom | Not specified |
| CNA | WSO2 | WSO2 Carbon OAuth | unaffected x * custom | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO... | ed10eef1-636d-4fbe-9993-6890dfa878f8 | security.docs.wso2.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
Additional Advisory Data
Solutions
CNA: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-3857/#solution
There are currently no legacy QID mappings associated with this CVE.