CVE-2026-35029: BerriAI LiteLLM Proxy /config/update Missing RBAC Privilege Escalation to RCE
A critical authorization failure in BerriAI LiteLLM proxy (< 1.83.9) enables any caller possessing a valid low-privileged or read-only virtual key to invoke the /config/update endpoint. By injecting custom configuration directives, an attacker can modify upstream model endpoints, inject malicious Python logging hooks, read local server files, and achieve unconstrained Remote Code Execution on the AI gateway infrastructure. Organizations using LiteLLM to broker multi-tenant LLM access must immediately upgrade to 1.83.9+.
HERMES THREAT SCORE & AGENTIC INFRASTRUCTURE EVALUATION
Target:BerriAI LiteLLM Proxy Configuration Engine (/config/update) While CVSS v3.1 rates this vulnerability at 8.8 because it requires an initial low-privileged virtual key (PR:L), the Hermes Threat Score elevates it to 91 (CRITICAL) with an Agentic HASS score of 94 (EXTREME). In enterprise AI architectures, thousands of autonomous coding and research agents are provisioned with low-privileged LiteLLM virtual keys. An adversary compromising a single agent can immediately escalate to full administrative compromise of the underlying inference cluster.
CVE-2026-35029: BerriAI LiteLLM Proxy /config/update Missing RBAC Privilege Escalation to RCEVULNERABILITY
Enterprise LLM proxy gateway supporting Model Context Protocol (MCP) streamable endpoints and unified LLM APIs.
๐ Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in LiteLLM Proxy & MCP Server documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
Vulnerability Analysis & Exploitation Mechanics
Section titled โVulnerability Analysis & Exploitation MechanicsโIn LiteLLM proxy deployments, virtual keys are used to enforce rate limits, cost allocations, and access permissions across development teams and autonomous agents.
Prior to version 1.83.9, the /config/update API route checked that the incoming request contained a valid authorization token, but failed to verify whether the caller possessed the proxy_admin role:
# Vulnerable pattern in litellm/proxy/proxy_server.py (< 1.83.9)@router.post("/config/update")async def update_config(data: ConfigUpdateRequest, user_api_key_dict: UserAPIKeyAuth = Depends(user_api_key_auth)): # FLAW: Only verified that user_api_key_dict exists, not user_role == "proxy_admin" return await proxy_config_manager.update_config(data)Remote Code Execution Path
Section titled โRemote Code Execution PathโBy submitting a crafted payload with a custom logging or pre-call callback module path, an attacker forces LiteLLMโs dynamic module loader to import and execute arbitrary Python code from the local filesystem or via Python module hooks:
POST /config/update HTTP/1.1Host: litellm.corp.internal:4000Authorization: Bearer sk-low-priv-agent-key-10928Content-Type: application/json
{ "general_settings": { "custom_callbacks": ["sys", "os.system('id > /tmp/pwned')"] }}Defensive Directives & Detection
Section titled โDefensive Directives & Detectionโ- Upgrade Immediately: Deploy LiteLLM version 1.83.9 or later.
- Restrict Management Endpoints: Ensure
/config/*,/key/*, and/team/*endpoints are inaccessible from public ingress controllers. - Audit Key Usage: Inspect proxy logs for POST requests to
/config/updateoriginating from non-admin virtual keys.