Improper Authentication Affecting litellm package, versions [1.91.0,1.100.4)[1.101.0,1.101.3)[1.102.0,1.102.2)[1.103.0,1.103.1)[1.104.0rc1,1.104.0rc2)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Improper Authentication vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-LITELLM-21433566
- published22 Oct 2026
- disclosed22 Oct 2026
- creditHoa X.
Introduced: 22 Oct 2026
NewCVE-2026-114612 (opens in a new tab)How to fix?
Upgrade litellm to version 1.100.4, 1.101.3, 1.102.2, 1.103.1, 1.104.0rc2 or higher.
Overview
litellm is a Library to easily interface with LLM API providers
Affected versions of this package are vulnerable to Improper Authentication via the UI/CLI session token encryption context in encrypt_value_helper (now encrypt_bearer_token) within litellm/proxy/common_utils/encrypt_decrypt_utils.py. Session tokens issued for the dashboard and CLI SSO flows are encrypted without a binding AES-GCM additional authenticated data (AAD) context, allowing an attacker who obtains a session token issued for one context (e.g. CLI) to replay it in another context (e.g. UI), bypassing the intended authentication boundary and gaining unauthorized access with the privileges of the original token holder. The fix binds UI and CLI session tokens to their own AES-GCM context by introducing a dedicated prefix as AAD, so tokens are cryptographically scoped and cannot be cross-replayed.
Note: Versions 1.87.0 through 1.90.x are only exploitable if EXPERIMENTAL_UI_LOGIN=true is explicitly set; versions 1.91.0 and later are exploitable in the default configuration.