CYBERSECURITYTRACKER
Permanent story citation

When LLM Gateways Go Wrong: Findings from LiteLLM

This page keeps the story as Cybersecurity Tracker first published it. If the tracker later corrects it, the correction appears below the original and never replaces it.

Back to newsStory 10137

As cited

Copy frozen at (site build).

vulnerabilities

When LLM Gateways Go Wrong: Findings from LiteLLM

A security assessment of LiteLLM, a widely deployed open-source language model gateway, identified multiple high-severity vulnerabilities tracked as CVE-2026-35029 and CVE-2026-59823. The flaws included missing role-based access control on the configuration update endpoint, allowing low-privileged users to modify proxy settings, inject malicious environment variables, and load arbitrary Python code for remote execution. A separate server-side request forgery vulnerability in the clientside credentials feature enabled attackers to redirect application programming interface (API) calls and extract provider keys.

Why it matters: Organizations deploying LiteLLM as a gateway for language model requests face compromise of stored credentials, administrative account takeover, and arbitrary code execution via an authenticated attacker with basic user privileges; upgrade to version 1.83.9 or later immediately to close these exposure paths.

VendorsAmazon Web ServicesCheck PointDocker
Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

When LLM Gateways Go Wrong: Findings from LiteLLM

A security assessment of LiteLLM, a widely deployed open-source language model gateway, identified multiple high-severity vulnerabilities tracked as CVE-2026-35029 and CVE-2026-59823. The flaws included missing role-based access control on the configuration update endpoint, allowing low-privileged users to modify proxy settings, inject malicious environment variables, and load arbitrary Python code for remote execution. A separate server-side request forgery vulnerability in the clientside credentials feature enabled attackers to redirect application programming interface (API) calls and extract provider keys.

Why it matters: Organizations deploying LiteLLM as a gateway for language model requests face compromise of stored credentials, administrative account takeover, and arbitrary code execution via an authenticated attacker with basic user privileges; upgrade to version 1.83.9 or later immediately to close these exposure paths.

VendorsAmazon Web ServicesCheck PointDocker
Source published
First seen by Cybersecurity Tracker

Source attribution

Glossary