LiteLLM - Information Disclosure (CVE-2026-35029)
Description
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.
psychologyCrowdSec Analysis
CVE-2026-35029 is a high-severity vulnerability in BerriAI's LiteLLM proxy server that allows authenticated users to access the /config/update endpoint without admin authorization. Exploiting this flaw, attackers can modify proxy configurations, execute arbitrary Python code, read sensitive server files, and even take over privileged accounts. This vulnerability could lead to remote code execution, information disclosure, and full compromise of the affected system. The issue is resolved in version 1.83.0.
CrowdSec has been tracking this vulnerability and its exploits since 6th of May 2026.
CrowdSec has not observed any significant exploitation activity targeting CVE-2026-35029 across its network. As a result, no community-driven trend analysis is available for this vulnerability at this time.
Attackers exploit the /config/update endpoint by sending crafted POST requests to configure the application to read arbitrary files, such as /etc/passwd, and exfiltrate their contents via attacker-controlled endpoints. This attack requires authentication but does not enforce admin role checks, allowing privilege escalation and sensitive file disclosure.
Full Intelligence Available
Connect your API key to access CrowdSec scores, exploit timelines, and attacker IPs.
| Event | Date |
|---|---|
| CVE Published | 2026-04-06 |
| Rule Released | 2026-05-06 |
| CrowdSec First Seen | 2026-06-09 |