CVE-2025-0330: LiteLLM Langfuse API Key Leakage
LiteLLM
LiteLLM contains a flaw where error handling during team settings parsing leaks Langfuse API credentials. This exposes full project access to unauthorized parties.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 7.5
- EPSS
- 0.01 · top 53% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 20 Mar 2025
- last update
- 20 Mar 2025
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2025-03-20CVE-2025-0330: LiteLLM Has a Leakage of Langfuse API KeysGitHub Advisory Database · github.com/advisories/GHSA-879v-fggm-vxw2
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerabilityData leak
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- mitre atlas
- no technique for these categories
- dates
- happened 20 Mar 2025 · first reported 20 Mar 2025
- origin
- GitHub Advisory DatabaseVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 07:00Z · updated 2026-10-18 07:00Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2025-0330: LiteLLM Langfuse API Key Leakage https://gcdradar.vercel.app/incidents/cve-2025-0330-litellm-langfuse-api-key-leakage · AIR-2025-0251 · closed 2025-03-20 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2025-03-20 - AI role: Attack on AI - Products: LiteLLM - CVE ids: CVE-2025-0330 - CVSS: 7.5 ## Summary LiteLLM contains a flaw where error handling during team settings parsing leaks Langfuse API credentials. This exposes full project access to unauthorized parties. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2025-03-20: CVE-2025-0330: LiteLLM Has a Leakage of Langfuse API Keys (https://github.com/advisories/GHSA-879v-fggm-vxw2) ## Sources - 2025-03-20 GitHub Advisory Database: CVE-2025-0330: LiteLLM Has a Leakage of Langfuse API Keys https://github.com/advisories/GHSA-879v-fggm-vxw2 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed7.5LiteLLM CVE-2024-9606: LiteLLM reveals portion of API key via logging file
Patch now · Disclosed · since 20 Mar 2025 · CVE-2024-9606
AI - closed8.7LiteLLM CVE-2026-89032: BerriAI LiteLLM semantic cache tenant isolation bypass
Patch now · Disclosed · since 25 Sep 2026 · CVE-2026-89032
AI - closed6.5LiteLLM CVE-2026-84377: LiteLLM Authenticated SSRF and Credential Exfiltration
Patch now · Disclosed · since 30 Sep 2026 · updated 30 Sep 2026 · CVE-2026-84377
AI - closed8.7LiteLLM CVE-2024-6587: LiteLLM Server-Side Request Forgery vulnerability
Patch now · Disclosed · since 13 Sep 2024 · CVE-2024-6587
AI - closedllama.cpp Misconfigured Llama.cpp Servers Expose Sensitive User Prompts
Breaches & attacks · Exploited · since 11 Apr 2025
AI - closed4.3Open WebUI Open WebUI Improper Access Control Leads to Arbitrary Prompt Read
Patch now · Disclosed · since 20 Mar 2025 · CVE-2024-7045
AI