Persistent account access via noninvalidated SSO tokens
Published Jun 21, 2026 · Updated Jun 21, 2026
Insufficient session expiration in LiteLLM 1.82.0 through 1.82.2 allows remote authenticated users to retain account access via old SSO tokens. The SSO redirect handler creates a new dashboard key at each login but does not delete, expire, or invalidate earlier keys for the same user. Exploitation requires a previously obtained UI session token and an SSO-enabled database deployment; reauthentication does not revoke the token before its absolute expiration.
Summary
What happened
Insufficient session expiration in LiteLLM 1.82.0 through 1.82.2 allows remote authenticated users to retain account access via old SSO tokens. The SSO redirect handler creates a new dashboard key at each login but does not delete, expire, or invalidate earlier keys for the same user. Exploitation requires a previously obtained UI session token and an SSO-enabled database deployment; reauthentication does not revoke the token before its absolute expiration.
The record
- CVE
- CVE-2026-12796
- Published
- Jun 21, 2026
- Updated
- Jun 21, 2026
- Vendor
- Berri AI
- Product
- LiteLLM
- Classifications
- CWE-613, T1550.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 21, 2026CVE publishedPublication date reported by the CVE source.
- Jun 21, 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=1.82.0
- Affected versionversion=1.82.1
- Affected versionversion=1.82.2
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- SSO UI token accumulation proof of conceptproof of concept · demonstrated
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo