CVE-2025-13173: Improper Token Revocation via Session-Bound Token Flow in Multiple WSO2 Products Allows Unauthorized Access After Session Termination

Severity: medium (CVSS 6.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-10-19 · updated 2026-10-20
Weakness: CWE-613

Description

Tokens associated with user sessions are not revoked when the corresponding user session is terminated, unless another SSO request is initiated. This occurs when the session-bound token feature is enabled with token binding validation and the "Revoke token upon user logout" option is not active. The software fails to automatically invalidate session-bound tokens upon user session termination. This vulnerability exists when token binding validation is enabled. As a result, a malicious actor possessing a valid session-bound token could exploit this condition to maintain unauthorized access to applications and resources even after the associated user session has ended, potentially leading to the exposure of sensitive user data.

Affected products

WSO2 API Manager: from 3.1.0 before 3.1.0.352; from 3.2.0 before 3.2.0.456; from 3.2.1 before 3.2.1.81; from 4.0.0 before 4.0.0.376; from 4.1.0 before 4.1.0.246; from 4.2.0 before 4.2.0.186 — fixed in 3.1.0.352, 3.2.0.456, 3.2.1.81, 4.0.0.376, 4.1.0.246, 4.2.0.186
WSO2 Identity Server: from 5.10.0 before 5.10.0.381; from 5.11.0 before 5.11.0.428; from 6.0.0 before 6.0.0.255; from 6.1.0 before 6.1.0.256; from 7.0.0 before 7.0.0.133; from 7.1.0 before 7.1.0.41 — fixed in 5.10.0.381, 5.11.0.428, 6.0.0.255, 6.1.0.256, 7.0.0.133, 7.1.0.41
WSO2 API Control Plane: from 4.5.0 before 4.5.0.47; from 4.6.0 before 4.6.0.13 — fixed in 4.5.0.47, 4.6.0.13
WSO2 Carbon OAuth: from 6.4.2 before 6.4.2.171; from 6.4.111 before 6.4.111.165; from 6.4.176 before 6.4.176.30; from 6.4.180 before 6.4.180.14; from 6.8.0 before 6.8.0.54; from 6.9.6 before 6.9.6.29 — fixed in 6.11.21.94, 6.13.16.21, 6.13.19.14, 6.13.27.10, 6.13.41.1, 6.4.111.165
WSO2 Identity Server as Key Manager: from 5.10.0 before 5.10.0.372 — fixed in 5.10.0.372
WSO2 Open Banking AM: from 2.0.0 before 2.0.0.401 — fixed in 2.0.0.401
WSO2 Open Banking IAM: from 2.0.0 before 2.0.0.421 — fixed in 2.0.0.421
WSO2 Traffic Manager: from 4.5.0 before 4.5.0.45; from 4.6.0 before 4.6.0.11 — fixed in 4.5.0.45, 4.6.0.11
WSO2 Universal Gateway: from 4.5.0 before 4.5.0.46; from 4.6.0 before 4.6.0.11 — fixed in 4.5.0.46, 4.6.0.11

How to fix

Upgrade to a fixed version: WSO2 API Manager 3.1.0.352, 3.2.0.456, 3.2.1.81, 4.0.0.376; WSO2 Identity Server 5.10.0.381, 5.11.0.428, 6.0.0.255, 6.1.0.256; WSO2 API Control Plane 4.5.0.47, 4.6.0.13; WSO2 Carbon OAuth 6.11.21.94, 6.13.16.21, 6.13.19.14, 6.13.27.10; WSO2 Identity Server as Key Manager 5.10.0.372; WSO2 Open Banking AM 2.0.0.401; WSO2 Open Banking IAM 2.0.0.421; WSO2 Traffic Manager 4.5.0.45, 4.6.0.11; WSO2 Universal Gateway 4.5.0.46, 4.6.0.11. Check the vendor advisory for mitigations.

References

https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4727/

Get alerted when CVE-2025-13173 or the next vulnerability affects your stack