Between June 29 and July 7, 2026, the Open Source Vulnerability (OSV) database published 16 advisories for the LiteLLM...
Between June 29 and July 7, 2026, the Open Source Vulnerability (OSV) database published 16 advisories for the LiteLLM library, covering critical security flaws such as authentication bypass (CVE-2026-49468), remote code execution (CVE-2026-42208, CVE-2024-6825), arbitrary file deletion (CVE-2024-4888), SQL injection (CVE-2024-4890, CVE-2024-5225), server-side request forgery (CVE-2024-6587), and API key leakage (CVE-2024-9606).
confidence score
Strong evidence: 2 independent source classes support this read.
signal brief
Between June 29 and July 7, 2026, the Open Source Vulnerability (OSV) database published 16 advisories for the LiteLLM library, covering critical security flaws such as authentication bypass (CVE-2026-49468), remote code execution (CVE-2026-42208, CVE-2024-6825), arbitrary file deletion (CVE-2024-4888), SQL injection (CVE-2024-4890, CVE-2024-5225), server-side request forgery (CVE-2024-6587), and API key leakage (CVE-2024-9606). These vulnerabilities affect versions prior to the latest release (1.91.2) and could allow attackers to compromise systems using LiteLLM, steal sensitive data, or execute arbitrary code. The rapid disclosure of multiple high-severity issues signals significant security debt in the project, potentially eroding developer trust and slowing adoption. The PyPI release 1.91.2 (July 11) may include fixes, but the surge in CVEs suggests ongoing risk.
What the sources said:
- OSV advisory GHSA-4xpc-pv4p-pm3w (June 16): "LiteLLM: Authentication Bypass via Host Header Injection" (source)
- OSV advisory PYSEC-2026-1541 (July 7): "LiteLLM Vulnerable to Remote Code Execution (RCE)" (source)
- OSV advisory PYSEC-2026-1546 (July 7): "LiteLLM Has an Improper Authorization Vulnerability" (source)
- OSV advisory PYSEC-2026-391 (June 29): "LiteLLM has SQL Injection in Proxy API key verification" (source)
source data used
“Library to easily interface with LLM API providers”
“Aliases: CVE-2026-49468, PYSEC-2026-388 LiteLLM: Authentication Bypass via Host Header Injection”
“Aliases: CVE-2024-4888, GHSA-3xr8-qfvj-9p9j Arbitrary file deletion in litellm”
“Aliases: CVE-2024-6825, GHSA-53gh-p8jc-7rg8 LiteLLM Vulnerable to Remote Code Execution (RCE)”
“Aliases: CVE-2024-4264, GHSA-7ggm-4rjg-594w litellm passes untrusted data to `eval` function without sanitization”
“Aliases: CVE-2025-0330, GHSA-879v-fggm-vxw2 LiteLLM Has a Leakage of Langfuse API Keys”
“Aliases: CVE-2024-4890, GHSA-8j42-pcfm-3467 SQL injection in litellm”
“Aliases: CVE-2024-8984, GHSA-fh2c-86xm-pm2x LiteLLM Vulnerable to Denial of Service (DoS) via Crafted HTTP Request”
“Aliases: CVE-2025-0628, GHSA-fjcf-3j3r-78rp LiteLLM Has an Improper Authorization Vulnerability”
“Aliases: CVE-2024-6587, GHSA-g26j-5385-hhw3 LiteLLM Server-Side Request Forgery (SSRF) vulnerability”
“Aliases: CVE-2024-9606, GHSA-g5pg-73fc-hjwq LiteLLM Reveals Portion of API Key via a Logging File”
“Aliases: CVE-2024-10188, GHSA-gw2q-qw9j-rgv7 LiteLLM Vulnerable to Denial of Service (DoS)”
“Aliases: CVE-2024-5225, GHSA-h6m6-jj8v-94jj SQL injection in litellm”
“Aliases: CVE-2024-5710, GHSA-qqcv-vg9f-5rr3 litellm vulnerable to improper access control in team management”
“Aliases: CVE-2024-2952, GHSA-46cm-pfwv-cgf8 LiteLLM has Server-Side Template Injection vulnerability in /completions endpoint”
“Aliases: CVE-2026-49468, GHSA-4xpc-pv4p-pm3w LiteLLM: Authentication Bypass via Host Header Injection”
“Aliases: CVE-2024-5751, GHSA-gppg-gqw8-wh9g litellm vulnerable to remote code execution based on using eval unsafely”
“Aliases: CVE-2026-35030, GHSA-jjhc-v7c2-5hh6 LiteLLM: Authentication bypass via OIDC userinfo cache key collision”
“Aliases: CVE-2026-42208, GHSA-r75f-5x8p-qvmc LiteLLM has SQL Injection in Proxy API key verification”
Decision support, not stock advice. This signal is research with cited evidence — not a recommendation to buy, sell, or hold any security.