CVE-2026-35029
Litellm remote code execution
- Published6 Apr 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:13545
- https://access.redhat.com/errata/RHSA-2026:28960
- https://access.redhat.com/errata/RHSA-2026:30056
- https://access.redhat.com/security/cve/CVE-2026-35029
- https://bugzilla.redhat.com/show_bug.cgi?id=2455474
- http://seclists.org/fulldisclosure/2026/Apr/17
- https://github.com/BerriAI/litellm/security/advisories/GHSA-53mr-6c8q-9789
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-35029.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-35029 being actively exploited?
CVE-2026-35029 is not in the CISA KEV catalog. Its EPSS exploit probability is 3.98%.
How severe is CVE-2026-35029?
CVE-2026-35029 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 3.98% probability of exploitation.
Which products are affected by CVE-2026-35029?
Affected products include Litellm.
How do I fix CVE-2026-35029?
Upgrade affected software to a fixed version, for example Litellm 1.83.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-35029 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.