AAK-MCP-LITELLM-CVE-2026-114612-001: LiteLLM from 1.87.0 below its fixed releases: session tokens share the at-rest encryption context, so an internal user can become proxy admin
- Severity
- CRITICAL
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
LiteLLMSessionTokenSharedEncryptionContext
What it detects
LiteLLM (litellm on PyPI; BerriAI/litellm), the LLM gateway proxy, sealed UI and CLI session tokens with encrypt_value_helper, the helper that seals its secrets at rest. From 1.87.0 the key API seals a key's callback_vars metadata with the same helper (#27141), and per the advisory the API-key flow returns what it sealed, so an authenticated internal_user can put a forged proxy_admin session in that metadata, have the proxy seal it, and present the result as a bearer token: the proxy opens it, trusts the forged administrator, and grants administrative access, including commands run through its MCP stdio endpoint (CVE-2026-114612, CVSS 3.1 9.9, CWE-269/CWE-345/CWE-441, GHSA-7hp6-4w63-5g45). 1.87.0 to 1.90.x accept such a token only when EXPERIMENTAL_UI_LOGIN is turned on; from 1.91.0 they accept it unless that variable is explicitly false. 1.100.4, 1.101.3, 1.102.2, 1.103.1 and 1.104.0rc2 seal session tokens through encrypt_bearer_token, under a prefix that is also the AES-GCM associated data, so a sealed secret no longer opens as a session.
How to fix
Upgrade litellm to a fixed release and pin it: 1.100.4, 1.101.3, 1.102.2 or 1.103.1 on those release lines, or 1.104.0 or later. A lower bound below 1.103.1 still admits affected releases (litellm>=1.100.4 admits 1.101.0 to 1.101.2, 1.102.0 to 1.102.1 and 1.103.0), so raise it to 1.103.1 or pin the exact version. Until you can upgrade, set EXPERIMENTAL_UI_LOGIN=false, which closes the path but also breaks CLI SSO and Claude Code gateway login.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-LITELLM-CVE-2026-114612-001
Limitations
Reports litellm from 1.87.0 below 1.100.4, and 1.101.0 to 1.101.2, 1.102.0 to 1.102.1 and 1.103.0, where a requirements*.txt (at any depth), or at the project root a pyproject.toml, Pipfile, Pipfile.lock, poetry.lock or uv.lock, or an MCP config's uvx launch states the version, reporting a range that admits an affected version (litellm>=1.100.4 admits 1.101.0). latest was 1.106.2 on 2026-10-23 and states no version, so a bare litellm is not reported. It reads the version, not the proxy's settings: 1.87.0 to 1.90.x are reported although they are exposed only with EXPERIMENTAL_UI_LOGIN turned on, and so is a later release run with it set to false. A pre-release reads as its release, so 1.104.0rc1 and the 1.104.0 dev releases, which are affected, read as 1.104.0, which is fixed, and are not reported, while 1.101.0rc1, 1.102.0rc1 and 1.103.0rc1 read as their affected releases and are. The ghcr.io/berriai/litellm image tag is not read, in a compose file or in an MCP config that starts it with docker run, and npm's litellm (zya/litellmjs, a JavaScript port on its own 0.x line) is another package and is not read. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.
References
- CVE: CVE-2026-114612
- OWASP MCP Top 10: MCP07:2025 (Insufficient Authentication & Authorization), MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
- OWASP Agentic Top 10: ASI03 (Identity and Privilege Abuse), ASI04 (Agentic Supply Chain Vulnerabilities), ASI05 (Unexpected Code Execution (RCE))
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-SUPPLY-08 (MCP-Specific Vuln)
- CSA AI Controls Matrix (AICM): IAM-01, STA-08
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-LITELLM-CVE-2026-114612-001.md: the page then shows that text, with the registry reference appended under it.