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

Overview

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

• api_control_plane >= 4.5.0 < 4.5.0.47
• api_control_plane >= 4.6.0 < 4.6.0.13
• universal_gateway >= 4.5.0 < 4.5.0.46
• universal_gateway >= 4.6.0 < 4.6.0.11
• api_manager >= 3.1.0 < 3.1.0.352
• api_manager >= 3.2.0 < 3.2.0.456
• api_manager >= 3.2.1 < 3.2.1.81
• api_manager >= 4.0.0 < 4.0.0.376
• api_manager >= 4.1.0 < 4.1.0.246
• api_manager >= 4.2.0 < 4.2.0.186
• api_manager >= 4.3.0 < 4.3.0.97
• api_manager >= 4.4.0 < 4.4.0.61
• api_manager >= 4.5.0 < 4.5.0.46
• api_manager >= 4.6.0 < 4.6.0.11
• traffic_manager >= 4.5.0 < 4.5.0.45
• traffic_manager >= 4.6.0 < 4.6.0.11
• identity_server_as_key_manager >= 5.10.0 < 5.10.0.372
• open_banking_iam >= 2.0.0 < 2.0.0.421
• open_banking_am >= 2.0.0 < 2.0.0.401
• identity_server >= 5.10.0 < 5.10.0.381
• identity_server >= 5.11.0 < 5.11.0.428
• identity_server >= 6.0.0 < 6.0.0.255
• identity_server >= 6.1.0 < 6.1.0.256
• identity_server >= 7.0.0 < 7.0.0.133
• identity_server >= 7.1.0 < 7.1.0.41
• identity_server >= 7.2.0 < 7.2.0.3
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 6.4.2 < 6.4.2.171
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 6.4.111 < 6.4.111.165
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 6.4.176 < 6.4.176.30
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 6.4.180 < 6.4.180.14
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 6.8.0 < 6.8.0.54
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 6.9.6 < 6.9.6.29
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 6.11.21 < 6.11.21.94
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 6.13.16 < 6.13.16.21
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 6.13.19 < 6.13.19.14
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 6.13.27 < 6.13.27.10
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 6.13.41 < 6.13.41.1
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 7.0.26 < 7.0.26.87
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 7.0.259 < 7.0.259.34
• org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth >= 7.0.385 < 7.0.385.3

Remediation

Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4727/#solution