LiteLLM Reveals Portion of API Key via a Logging File
Published 20 Mar 2025 · Updated 10 Sept 2026
Is your project on an affected litellm?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <1.44.12
- Fixed in
- 1.44.12
pip install 'litellm>=1.44.12'Details
In berriai/litellm before version 1.44.12, the litellm/litellm_core_utils/litellm_logging.py file contains a vulnerability where the API key masking code only masks the first 5 characters of the key. This results in the leakage of almost the entire API key in the logs, exposing a significant amount of the secret key. The issue affects version v1.44.9.
Is GHSA-g5pg-73fc-hjwq in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected litellm, and gives you the command that fixes it.
More advisories for litellm
- HighGHSA-g5ff-637f-6q2mLiteLLM: internal_user_viewer arbitrary local file read via `vertex_ai_credentials` · 27 Oct 2026
- MediumGHSA-hhww-mrg2-969hLiteLLM vulnerable to reflected XSS in /sso/debug/callback · 27 Oct 2026
- HighCVE-2026-114612LiteLLM: Privilege Escalation to Proxy Admin via Cross-Domain Reuse of the Salt Key · 27 Oct 2026
- MediumCVE-2026-84377LiteLLM: Authenticated SSRF and provider-credential exfiltration via unvalidated request-body routing parameters · 30 Sept 2026
- MediumCVE-2026-59823LiteLLM Proxy has server-side request forgery via the `user_config` request parameter · 17 Sept 2026
- CriticalCVE-2026-37004LiteLLM vulnerable to server-side template injection in the /prompts/test endpoint · 27 Aug 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.