CVE-2026-12796: litellm SSO Session Expiration Vulnerability (CVSS 6.3)
A flaw in BerriAI's litellm SSO authentication system allows authenticated users to trigger session expiration through manipulation of the OpenID redirect response handler. The vulnerability is network-accessible, requires valid credentials to exploit, and poses a moderate risk to applications relying on litellm's proxy authentication layer. Public exploit code exists, though no evidence of active weaponization in ransomware campaigns has been reported.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- Weaknesses (CWE)
- CWE-613
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-21 / 2026-06-24
NVD description (verbatim)
A vulnerability was identified in BerriAI litellm up to 1.82.2. This impacts the function get_redirect_response_from_openid of the file litellm/proxy/management_endpoints/ui_sso.py of the component SSO Authentication Flow. The manipulation leads to session expiration. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure.
5 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-12796 exists in the SSO authentication flow component of litellm's proxy management endpoints, specifically within the get_redirect_response_from_openid function in litellm/proxy/management_endpoints/ui_sso.py. The vulnerability allows manipulation of OpenID redirect responses, resulting in unauthorized session expiration. The flaw stems from improper session state validation (CWE-613: Insufficient Session Expiration) and is exploitable by any authenticated user without requiring user interaction or special system privileges. The attack surface is remote, making it actionable from network-accessible deployments.
Business impact
Session expiration attacks disrupt service availability for legitimate users and can create a vector for account takeover when combined with phishing or credential compromise. Organizations using litellm as an API gateway or authentication proxy may experience degraded user experience, forced re-authentication loops, and potential denial of service if exploit activity targets multiple concurrent sessions. The impact is especially acute in multi-tenant environments where users share the same SSO endpoint.
Affected systems
BerriAI litellm versions up to and including 1.82.2 are confirmed vulnerable. Organizations should verify their deployment version immediately. The vulnerability affects deployments that enable SSO authentication via the proxy management endpoints; non-SSO configurations or isolated offline deployments face lower risk. Check your litellm version with 'pip show litellm' or equivalent package manager query.
Exploitability
The vulnerability is remotely exploitable with low complexity and low attack overhead—only valid user authentication is required. Public exploit code availability increases the likelihood of opportunistic attacks, though the requirement for authenticated access limits blast radius compared to unauthenticated flaws. Attack speed is fast once credentials are obtained, making detection and response velocity critical.
Remediation
Upgrade litellm to a patched version released after the June 24, 2026 modification date. Verify the patch version with the BerriAI project maintainers or official release notes. Interim mitigations include restricting SSO proxy access to trusted networks, monitoring session logs for anomalous expiration patterns, and implementing rate limiting on authentication endpoints to slow exploitation attempts.
Patch guidance
Check the BerriAI litellm repository (GitHub: BerriAI/litellm) for releases newer than 1.82.2. Upgrade using 'pip install --upgrade litellm' and verify the installed version post-deployment. Test SSO functionality in a staging environment before production rollout. If patch availability is delayed, consult the vendor's security advisory for temporary workarounds or configuration hardening steps.
Detection guidance
Monitor authentication logs for unusual session termination patterns, particularly clusters of expiration events from the same user or IP within short timeframes. Search proxy logs for repeated requests to the /sso or OpenID redirect endpoints with subsequent 401/403 responses. Implement alerting on session_expired events correlated with OpenID callback processing. Review litellm proxy access logs for evidence of the get_redirect_response_from_openid function being called with malformed or unexpected parameters.
Why prioritize this
CVSS 6.3 (MEDIUM) reflects confidentiality, integrity, and availability impact with low attack complexity, but the requirement for prior authentication prevents critical severity. However, public exploit availability and the focus on session integrity—a core security control—warrant priority patching. Organizations running production SSO proxies should patch within 30 days; those with internet-exposed litellm instances should treat it as urgent.
Risk score, explained
The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L) assigns MEDIUM severity because the attack is network-accessible with no user interaction, but it mandates low-privileged authentication. The flaw impacts three security dimensions (confidentiality, integrity, availability) at low severity each—typical of session-layer attacks—yielding a 6.3 base score. The presence of public exploits increases operational risk above the baseline CVSS, and the lack of KEV designation suggests no current mass-exploitation reports.
Frequently asked questions
Does this vulnerability affect litellm if we're not using SSO?
The flaw is specific to the SSO authentication flow. If your deployment relies solely on API key authentication or does not expose the proxy management endpoints, risk is significantly lower. However, upgrading remains prudent for defense-in-depth and to eliminate potential lateral attack vectors in multi-feature deployments.
What does 'session expiration' mean in this context—does it log me out?
Yes. An authenticated attacker can manipulate OpenID responses to force unexpected session termination, logging out legitimate users. This is distinct from normal timeout-based expiration and can be triggered repeatedly to disrupt service or enable credential-stuffing attacks when users re-authenticate.
Is this in CISA's Known Exploited Vulnerabilities catalog?
No. CVE-2026-12796 is not currently on the KEV list, indicating no confirmed active exploitation by threat actors at scale. However, public proof-of-concept code exists, so organizations should treat it as a medium-term risk rather than an emergency unless your environment is known to be targeted.
Can we temporarily disable SSO to mitigate this?
Yes. If your operational setup permits, disabling the SSO proxy endpoints or restricting access to trusted networks only is a valid short-term workaround while you plan upgrades. Test any configuration changes in staging first to ensure authentication flows remain functional for your users.
This analysis is provided for informational purposes and does not constitute legal, security, or investment advice. Patch versions, vendor advisories, and exploit availability are subject to change; verify current status with BerriAI's official channels and your security team. Deploying any security fix should be tested in non-production environments first. SEC.co and its authors assume no liability for errors, omissions, or decisions made based on this content. Source: NVD (public-domain), retrieved 2026-07-28. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-12772MEDIUMSession Expiration Flaw in BerriAI litellm Proxy Authentication
- CVE-2026-44188MEDIUMAnsible Lightspeed Session Hijacking via Token Non-Revocation
- CVE-2026-48726MEDIUMApache Airflow JWT Token Revocation Bypass in FAB and Keycloak Logout
- CVE-2026-53824MEDIUMOpenClaw Token Revocation Bypass (CVSS 6.5)
- CVE-2026-53830MEDIUMOpenClaw Webhook Secret Revocation Bypass (CVSS 6.5)
- CVE-2026-55423MEDIUMLangflow Session Invalidation Flaw—Impact, Patch & Detection
- CVE-2026-9802MEDIUMKeycloak Refresh Token Replay After Revocation
- CVE-2025-62340LOWHCL iControl Session Timeout Vulnerability – Analysis & Remediation