AI Stack Alert High CVE-2026-114612 For AI Eng, AppSec, SOC / IR, CISO AI-assisted
LiteLLM proxy privilege escalation to proxy_admin via reused salt key (CVE-2026-114612)
A flaw in LiteLLM lets an authenticated internal_user escalate to proxy_admin and reach remote code execution. The proxy uses one encryption key both to seal secrets at rest and to mint session tokens, so a crafted value can be accepted as a valid admin bearer token. Patched versions are 1.100.4, 1.101.3, 1.102.2, 1.103.1, and 1.104.0rc2.
Why it matters
Any internal user with a low-privilege account can gain full proxy admin rights and run arbitrary commands on the host through the MCP stdio endpoint. Organizations running affected LiteLLM versions in default configuration are exposed.
Do this
- Upgrade LiteLLM to the fixed release for your branch: 1.100.4, 1.101.3, 1.102.2, 1.103.1, or 1.104.0rc2.
- If you cannot upgrade immediately, set EXPERIMENTAL_UI_LOGIN=false, and plan for broken CLI SSO and Claude Code gateway login while this is in place.
- Review the list of internal_user accounts and remove or restrict any that do not need proxy access.
- Audit proxy logs for API key creation requests with unusual metadata values and for unexpected proxy_admin actions or MCP stdio command execution.
Exploit Clock
Exploitation unlikely (for now)
- EPSS 0.32%
Signals
- NoCISA KEV
- 9.9CVSS
- 0.32%EPSS
- 36/100Priority
- 80%Confidence
Evidence
“An authenticated user with `internal_user` privileges can escalate to `proxy_admin` and achieve remote code execution.”
“The proxy uses one encryption key for two purposes: sealing secrets at rest and minting session tokens.”
“Versions later than 1.91.0 are exploitable in the default configuration.”
“This disables the vulnerable authentication path but also breaks CLI SSO and Claude Code gateway login.”
Sources
Affected / related
LiteLLM, LiteLLM proxy, MCP stdio endpoint
Published 2026-10-27 15:04 UTC · updated 2026-11-08 02:40 UTC · AI-assisted summary, checked against quoted sources · How we score