Post-logout access via misrouted session token deletion
Published Sep 28, 2026 · Updated Sep 28, 2026
Session revocation failure in SUSE Rancher 2.15.0 through 2.15.1 allows remote attackers with a captured token to retain API access after logout. The logout handler clears browser cookies but passes the wrong token identifier to deletion logic, leaving the public API session token in its backing store. Exploitation requires a previously captured victim token, a subsequent victim logout, and a deployment using public API session tokens; access lasts until token expiry.
Summary
What happened
Session revocation failure in SUSE Rancher 2.15.0 through 2.15.1 allows remote attackers with a captured token to retain API access after logout. The logout handler clears browser cookies but passes the wrong token identifier to deletion logic, leaving the public API session token in its backing store. Exploitation requires a previously captured victim token, a subsequent victim logout, and a deployment using public API session tokens; access lasts until token expiry.
The record
- CVE
- CVE-2026-88805
- Published
- Sep 28, 2026
- Updated
- Sep 28, 2026
- Vendor
- SUSE
- Product
- Rancher
- Classifications
- CWE-613, CWE-287, T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 28, 2026CVE publishedPublication date reported by the CVE source.
- Sep 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.15.0 <2.15.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started