CVE-2026-114612: LiteLLM: Privilege Escalation to Proxy Admin via Cross-Domain Reuse of the Salt Key
Summary
An authenticated user with internaluser privileges can escalate to proxyadmin and achieve remote code execution. The proxy uses one encryption key for two purposes: sealing secrets at rest and minting session tokens. An attacker exploits this by requesting a new API key with a crafted metadata field containing a forged admin credential as the "secret" value. The proxy encrypts and returns this payload. When this value is then presented as a bearer token, the proxy decrypts it, trusts the forged admin identity, and grants full administrative access, including the ability to execute arbitrary commands via the MCP stdio endpoint.
Affected versions
Versions later than 1.91.0 are exploitable in the default configuration. Versions 1.87.0 through 1.90.x are exploitable only if EXPERIMENTALUILOGIN=true was explicitly set.
Mitigation
Upgrade to a patched version as soon as possible.
If you cannot upgrade immediately, set EXPERIMENTALUILOGIN=false. This disables the vulnerable authentication path but also breaks CLI SSO and Claude Code gateway login.
Impact
An internal user can escalate to proxy admin and execute arbitrary commands on the host.
Discovery Credit: Hoa X. Nguyen (OPSWAT Unit 515)
Other sources
LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. From 1.87.0 until 1.100.4, 1.101.3, 1.102.2, 1.103.1, and 1.104.0-rc.2, the proxy reuses one cryptographic context for at-rest secrets and session tokens, allowing an authenticated internal user to have crafted metadata containing a forged administrator credential encrypted and returned by the API-key flow. Replaying that ciphertext as a bearer token causes the proxy to trust the forged proxy administrator identity, permitting administrative access and arbitrary commands through the MCP stdio endpoint. Versions 1.87.0 through 1.90.x require EXPERIMENTALUILOGIN to be enabled, while versions after 1.91.0 are exploitable in the default configuration. This issue was fixed in LiteLLM 1.100.4, 1.101.3, 1.102.2, 1.103.1, and 1.104.0-rc.2.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/litellmto a version that resolves this vulnerability.Fixed in 1.104.0rc2 - Upgrade
Upgrade
pip/litellmto a version that resolves this vulnerability.Fixed in 1.103.1 - Upgrade
Upgrade
pip/litellmto a version that resolves this vulnerability.Fixed in 1.102.2 - Upgrade
Upgrade
pip/litellmto a version that resolves this vulnerability.Fixed in 1.101.3 - Upgrade
Upgrade
pip/litellmto a version that resolves this vulnerability.Fixed in 1.100.4 - Upgrade
Upgrade
LiteLLMto a version that resolves this vulnerability.Fixed in 1.100.4 - Upgrade
Upgrade
LiteLLMto a version that resolves this vulnerability.Fixed in 1.101.3 - Upgrade
Upgrade
LiteLLMto a version that resolves this vulnerability.Fixed in 1.102.2 - Upgrade
Upgrade
LiteLLMto a version that resolves this vulnerability.Fixed in 1.103.1 - Upgrade
Upgrade
LiteLLMto a version that resolves this vulnerability.Fixed in 1.104.0-rc.2 - Configuration
Set EXPERIMENTAL_UI_LOGIN=false if you cannot upgrade immediately; this disables the vulnerable authentication path but breaks CLI SSO and Claude Code gateway login.
LiteLLM EXPERIMENTAL_UI_LOGIN = false
Event History
Frequently Asked Questions
Which deployments are exposed by default?
LiteLLM versions after 1.91.0 in the affected ranges are exploitable in the default configuration. Versions 1.87.0 through 1.90.x require EXPERIMENTAL_UI_LOGIN to be enabled.
What level of access does an attacker need?
An attacker must be an authenticated internal user. They need to submit crafted metadata through the API-key flow, obtain the resulting encrypted credential, and replay it as a bearer token.
What access can successful exploitation provide?
Successful exploitation causes the proxy to trust a forged proxy administrator identity. This grants administrative access and permits arbitrary commands through the MCP stdio endpoint.
Which versions contain fixes?
The issue is fixed in LiteLLM 1.100.4, 1.101.3, 1.102.2, 1.103.1, and 1.104.0-rc.2.