Unknown severity · Source severity not reportedCVE-2025-0326

Improper Token Revocation in WSO2 Identity Server Allows Unauthorized AccessCVE-2025-0326

Answer in brief

CVE-2025-0326 records a Unknown severity vulnerability in Improper Token Revocation in WSO2 Identity Server Allows Unauthorized Access. The current sources do not mark it as known exploited. The current feed maps WSO2/WSO2 Carbon OAuth (generic), WSO2/WSO2 Identity Server (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 21, 2026Updated Oct 21, 2026Source checked Oct 21, 2026First seen by HOL Oct 21, 2026Material review Oct 21, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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.

Affected scope and exposure questions

The current feed maps WSO2/WSO2 Carbon OAuth (generic), WSO2/WSO2 Identity Server (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
WSO2/WSO2 Carbon OAuthgeneric	>=7.0.26 <7.0.26.51	7.0.26.51
WSO2/WSO2 Identity Servergeneric	>=7.0.0 <7.0.0.85	7.0.0.85

Recommended response

Check inventory. Check lockfiles and deployed manifests for WSO2/WSO2 Carbon OAuth, WSO2/WSO2 Identity Server.
Review the reported fix. Source-reported solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-3857/#solution

Evidence timeline and material changes

Published upstream
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 21, 2026

Sources and claim methodology

Source referencesecurity.docs.wso2.com

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.