CVE-2025-0326
Improper Token Revocation in WSO2 Identity Server Allows Unauthorized Access
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.
INFO
Published Date :
Oct. 21, 2026, 2:17 p.m.
Last Modified :
Oct. 21, 2026, 2:17 p.m.
Remotely Exploit :
No
Source :
ed10eef1-636d-4fbe-9993-6890dfa878f8
Solution
- Update access token invalidation logic for user management.
- Ensure tokens are revoked on password reset.
- Ensure tokens are revoked on role changes.
- Ensure tokens are revoked on sub-organization disablement.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-0326.
| URL | Resource |
|---|---|
| https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-3857/ |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-0326 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-0326
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-0326 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-0326 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by ed10eef1-636d-4fbe-9993-6890dfa878f8
Oct. 21, 2026
Action Type Old Value New Value Added 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. Added CWE CWE-613 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2025/0xxx/CVE-2025-0326.json">CVE-2025-0326</a> Added Reference https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-3857/