All vulnerabilities

Servers and applications

CVE-2026-88805

Session Not Revoked Server-Side on Logout in Rancher

Severity
High 7.4
Published
23 Sept 2026
Last changed
23 Sept 2026
Added to UpHeron
3 Nov 2026
Fixed in
2.15.2
Exploit chance
0.3% in the next 30 daysHigher than 16% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Improper authentication (CWE-287)Insufficient session expiration (CWE-613)
Attack
Over the network · Only under certain conditions · No login needed · Needs someone to click or open something
Attacker can
Read data · Change data
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Also known as
GHSA-6vpq-mf48-9794
Sources
Project advisories (GitHub)

Description

A session revocation vulnerability exists in Rancher's logout handling for public API session tokens. When a user logs out of the Rancher UI, the browser session cookies are cleared, but the corresponding server-side session token is not removed from its backing store. As a result, the session token remains valid and continues to authenticate API requests until its configured time-to-live or idle timeout expires.

Logout is the primary control available to users and administrators to immediately terminate a session that is suspected to be compromised. Because this control does not take effect server-side, a session that a user believes to have been terminated can still be used.

Exploitation of this issue requires the following conditions:

  • Rancher is configured with an authentication provider that issues external session tokens (for example, OIDC-based providers such as Generic OIDC, Keycloak, or Azure AD).
From rancher/rancher's security advisory. Shortened; the full text is there.

Workarounds

There is no complete workaround other than upgrading to a patched version.

If organizations are unable to upgrade immediately, some partial mitigations are:

  • Reduce the session token time-to-live and idle timeout settings in Rancher so that a session that is not revoked at logout expires sooner.
  • Administrators can delete the affected user's active session tokens directly (for example, by removing the user's tokens through the Rancher API or by disabling the user account) when immediate revocation is required.
Workarounds as given by rancher/rancher's security advisory.

Affected software

SoftwareAffected versions
RancherServers and applications · github:rancher/rancher
  • From 2.15.0 before 2.15.2

About Rancher

Complete container management platform

From its GitHub repository.
Teams using it daily
More than 30,000Rancher
Docker Hub pulls
320,721,144Docker Hub, 15 Nov 2026
GitHub stars
26,057GitHub, 15 Nov 2026
Forks
3,226GitHub, 15 Nov 2026
Latest release
v2.15.3GitHub, 15 Nov 2026
Released
29 Oct 2026GitHub
License
Apache-2.0GitHub
First published on GitHub
7 Nov 2014GitHub

Release lines

ReleaseLatestSecurity fixes
2.152.15.3Until 27 Feb 2028
2.142.14.7Until 10 Oct 2027
2.132.13.11Until 17 Jun 2027
2.122.12.15Until 28 Feb 2027
2.112.11.19Ended 24 Oct 2026
2.102.10.12Ended 19 Jun 2026

From endoflife.date.

References