CVE-2026-35029: LiteLLM affected by privilege escalation via unrestricted proxy configuration endpoint
LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.83.0, the /config/update endpoint does not enforce admin role authorization. A user who is already authenticated into the platform can then use this endpoint to modify proxy configuration and environment variables, register custom pass-through endpoint handlers pointing to attacker-controlled Python code, achieving remote code execution, read arbitrary server files by setting UI_LOGO_PATH and fetching via /get_image, and take over other privileged accounts by overwriting UI_USERNAME and UI_PASSWORD environment variables. Fixed in v1.83.0.
Security readout for executives and security teams
Plain-English summary
LiteLLM versions before 1.83.0 let any authenticated platform user change proxy configuration without admin authorization. That can escalate a low-privileged account into control of the AI gateway, including remote code execution, server file reads, and takeover of privileged UI accounts.
Executive priority
Treat this as urgent for any LiteLLM gateway with multiple users or network exposure. A compromised ordinary account could become control of the AI proxy and underlying server context.
Technical view
The vulnerable /config/update endpoint lacks proper admin role enforcement. With valid authentication, an attacker can alter proxy configuration and environment variables, register custom pass-through endpoint handlers, abuse UI_LOGO_PATH for file reads via /get_image, and overwrite UI_USERNAME/UI_PASSWORD. The issue is fixed in LiteLLM 1.83.0.
Likely exposure
Exposure is limited to deployments running BerriAI LiteLLM before 1.83.0 where untrusted or lower-privileged users can authenticate. Internet exposure of the LiteLLM proxy or broad internal user access increases risk.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation evidence. Exploitation requires a valid authenticated account, but no user interaction and low complexity are indicated by CVSS 3.1 score 8.8.
Researcher notes
Focus validation on authorization bypass at /config/update, configuration drift, environment-variable changes, unexpected handler registrations, and file-access indicators through /get_image. Avoid assuming unauthenticated exposure; the source description requires an already authenticated user.
Mitigation direction
Upgrade LiteLLM to version 1.83.0 or later.
Restrict LiteLLM administrative and management surfaces to trusted administrators.
Review vendor and Red Hat advisories for product-specific packages and errata.
Rotate administrative credentials and connected secrets if suspicious configuration changes are found.
Validation and detection
Inventory all LiteLLM deployments and confirm installed versions.
Review logs for non-admin requests to /config/update.
Check for unexpected custom pass-through handlers or environment-variable overrides.
Verify UI_USERNAME, UI_PASSWORD, and UI_LOGO_PATH were not unexpectedly changed.
Confirm Red Hat affected products are remediated through applicable errata.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-425: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
3ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-425 · source CWE mapping
Direct Request ('Forced Browsing')
Direct Request ('Forced Browsing') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.