Skip to main content

CVE-2025-0326: CWE-613: Insufficient Session Expiration in WSO2 WSO2 Identity Server

0
Medium
Published: 10/21/2026 (10/21/2026, 15:42:31 UTC)
Source: CVE Database V5
Vendor/Project: WSO2
Product: WSO2 Identity Server

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.

Affected software

WSO2

WSO2 Identity Server

Affected versions
>=7.0.0 <7.0.0.85

WSO2

WSO2 Carbon OAuth

Affected versions
>=7.0.26 <7.0.26.51
org.wso2.identity.server/wso2-identity-server
pkg:maven/org.wso2.identity.server/wso2-identity-server
Affected versions
>=7.0.0 <7.0.0.85>=7.0.26 <7.0.26.51

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/21/2026, 14:16:31 UTC

Technical Analysis

CVE-2025-0326 describes a vulnerability in WSO2 Identity Server where access tokens associated with sub-organization users are not invalidated during critical account management operations. This insufficient session expiration (CWE-613) means that tokens remain valid even after password resets, role changes, or sub-organization disablement, potentially allowing unauthorized access if those tokens are exposed to malicious actors. The vulnerability affects versions >=7.0.0 <7.0.0.85 and >=7.0.26 <7.0.26.51.

Potential Impact

If exploited, an attacker who has obtained previously issued access tokens could maintain unauthorized access to resources even after administrative actions intended to revoke or modify user access. However, exploitation requires that the tokens remain active and are exposed to malicious actors. There are no known exploits in the wild at this time.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Until a patch is available, organizations should consider additional controls around token exposure and monitor for suspicious token usage related to sub-organization users undergoing sensitive account changes.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
WSO2
Date Reserved
2025-01-08T13:19:11.080Z
State
PUBLISHED

Threat ID: 6ad8c5a24d27ba8daab0d960

Added to database: 10/21/2026, 14:01:06 UTC

Last enriched: 10/21/2026, 14:16:31 UTC

Last updated: 10/21/2026, 20:13:07 UTC

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses