# CVE-2025-13173: WSO2 products session-bound token improper revocation

Source: https://junglewise.ai/threats/cve-2025-13173-tokens-associated-with-user-sessions-are-not-revoked-when-the  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-19. Updated: 2026-10-19  
License: CC BY 4.0 with a link back

CVE-2025-13173 · Severity: medium · CVSS 6.5 · Published 2026-10-19

WSO2's identity and API management products fail to revoke session-bound authentication tokens when a user logs out, provided a specific token binding configuration is enabled. An attacker with a valid token can remain authenticated to protected applications and resources even after the legitimate user's session ends, potentially exposing sensitive data or allowing account takeover.

Technologies: [Wso2 API Control Plane](https://junglewise.ai/threats/technologies/api-control-plane), [Wso2 API Manager](https://junglewise.ai/threats/technologies/api-manager), [Wso2 Identity Server](https://junglewise.ai/threats/technologies/identity-server), [Wso2 Identity Server as Key Manager](https://junglewise.ai/threats/technologies/identity-server-as-key-manager), [Wso2 Open Banking AM](https://junglewise.ai/threats/technologies/open-banking-am), [Wso2 Open Banking IAM](https://junglewise.ai/threats/technologies/open-banking-iam), [Wso2 Traffic Manager](https://junglewise.ai/threats/technologies/traffic-manager), [Wso2 Universal Gateway](https://junglewise.ai/threats/technologies/universal-gateway). Vendors: [Wso2](https://junglewise.ai/threats/vendors/wso2).

## Quick answers

**Is CVE-2025-13173 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-13173 being exploited in the wild.

**How severe is CVE-2025-13173?** Medium severity, with a CVSS score of 6.5, published 19 October 2026.

**Which products and versions are affected?** Wso2 API Control Plane 4.6.0, 4.5.0; Wso2 API Manager 4.6.0, 4.5.0, 4.4.0, 4.3.0, 4.2.0, 4.1.0, 4.0.0, 3.2.1, 3.2.0, 3.1.0; Wso2 Identity Server 7.2.0, 7.1.0, 7.0.0, 6.1.0, 6.0.0, 5.11.0, 5.10.0; Wso2 Identity Server as Key Manager 5.10.0; and 4 more.

**Is there a fix for CVE-2025-13173?** Yes: fixed in WSO2 API Control Plane 4.6.0 update 12+, 4.5.0 update 47+; WSO2 API Manager 4.6.0 update 11+, 4.5.0 update 46+, 4.4.0 update 61+, 4.3.0 update 97+, 4.2.0 update 186+, 4.1.0 update 246+, 4.0.0 update 376+, 3.2.1 update 81+, 3.2.0 update 456+, 3.1.0 update 352+; WSO2 Identity Server 7.2.0 update 3+, 7.1.0 update 41+, 7.0.0 update 133+, 6.1.0 update 256+, 6.0.0 update 255+, 5.11.0 update 428+, 5.10.0 update 381+; WSO2 Identity Server as Key Manager 5.10.0 update 372+; WSO2 Open Banking AM 2.0.0 update 401+; WSO2 Open Banking IAM 2.0.0 update 421+; WSO2 Traffic Manager 4.6.0 update 11+, 4.5.0 update 45+; WSO2 Universal Gateway 4.6.0 update 11+, 4.5.0 update 46+. Until then: Ensure the "Revoke token upon user logout" option is enabled in the application protocol configuration when session-bound token binding is used. Alternatively, disable the session-bound token feature if it is not required for your deployment. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2025-13173 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2025-13173?** Check whether you run Wso2 API Control Plane, Wso2 API Manager, Wso2 Identity Server or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in WSO2 API Control Plane 4.6.0 update 12+, 4.5.0 update 47+; WSO2 API Manager 4.6.0 update 11+, 4.5.0 update 46+, 4.4.0 update 61+, 4.3.0 update 97+, 4.2.0 update 186+, 4.1.0 update 246+, 4.0.0 update 376+, 3.2.1 update 81+, 3.2.0 update 456+, 3.1.0 update 352+; WSO2 Identity Server 7.2.0 update 3+, 7.1.0 update 41+, 7.0.0 update 133+, 6.1.0 update 256+, 6.0.0 update 255+, 5.11.0 update 428+, 5.10.0 update 381+; WSO2 Identity Server as Key Manager 5.10.0 update 372+; WSO2 Open Banking AM 2.0.0 update 401+; WSO2 Open Banking IAM 2.0.0 update 421+; WSO2 Traffic Manager 4.6.0 update 11+, 4.5.0 update 45+; WSO2 Universal Gateway 4.6.0 update 11+, 4.5.0 update 46+

Ensure the "Revoke token upon user logout" option is enabled in the application protocol configuration when session-bound token binding is used. Alternatively, disable the session-bound token feature if it is not required for your deployment.

## Technical details

The session-bound token feature, when enabled with token binding validation and without the "Revoke token upon user logout" option active, fails to invalidate tokens upon session termination. An unauthenticated network attacker can exploit this by possessing a valid session-bound token to maintain unauthorized access. The vulnerability requires the feature to be explicitly enabled via console configuration.

## Affected products

- WSO2 API Control Plane 4.6.0, 4.5.0
- WSO2 API Manager 4.6.0, 4.5.0, 4.4.0, 4.3.0, 4.2.0, 4.1.0, 4.0.0, 3.2.1, 3.2.0, 3.1.0
- WSO2 Identity Server 7.2.0, 7.1.0, 7.0.0, 6.1.0, 6.0.0, 5.11.0, 5.10.0
- WSO2 Identity Server as Key Manager 5.10.0
- WSO2 Open Banking AM 2.0.0
- WSO2 Open Banking IAM 2.0.0
- WSO2 Traffic Manager 4.6.0, 4.5.0
- WSO2 Universal Gateway 4.6.0, 4.5.0

## Timeline

- 2026-05-03: advisory

## References

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

## Related threats

- [WSO2 Identity Server privilege escalation via client credentials grant type](https://junglewise.ai/threats/cve-2025-11229-the-system-fails-to-properly-enforce-scope-authorization-when-the)
- [WSO2 Identity Server privilege escalation via shared database](https://junglewise.ai/threats/cve-2026-4052-this-issue-only-impacts-deployments-where-wso2-identity-server-is)
- [WSO2 Access token issuance without IDP status validation](https://junglewise.ai/threats/cve-2025-1397-when-utilizing-jwt-bearer-or-saml2-bearer-grant-types-the-system)
- [WSO2 API Manager Admin REST API SQL injection](https://junglewise.ai/threats/cve-2026-2613-the-admin-rest-api-accepts-user-supplied-input-without-adequately)
- [WSO2 API Manager SVG upload stored XSS in Publisher portal](https://junglewise.ai/threats/cve-2025-12544-the-publisher-portal-fails-to-enforce-proper-validation-on)