---
id: "CVE-2025-13173"
kind: "vulnerability"
aliases: ["CVE-2025-13173"]
title: "Session-bound tokens survive logout unless token revocation option is enabled"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["other", "session-management", "sso"]
not_affected_if: ["default-config"]
published_at: "2026-10-19T17:16:59+00:00"
first_seen_at: "2026-10-23T21:57:18+00:00"
updated_at: "2026-10-25T03:55:53+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-13173", "first_seen_at": "2026-10-23T21:57:18+00:00"}]
---

# Session-bound tokens survive logout unless token revocation option is enabled

When session-bound token binding validation is enabled, tokens tied to a user session are not revoked when that session ends, unless another SSO request is made. An attacker holding such a token can keep accessing applications and resources after the user has logged out, potentially exposing sensitive user data.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether session-bound token feature with token binding validation is enabled in the SSO product configuration: unknown
- Check whether the "Revoke token upon user logout" option is active: unknown

## Timeline

- 2026-10-23T21:57:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2025-13173

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_