Summary
LiteLLM: Local file read via request-supplied OIDC file references
Workarounds
Restrict /health/test_connection access to trusted administrators only.
Impact
LiteLLM's /health/test_connection endpoint resolved request-supplied environment and OIDC file references in litellm_params. A proxy administrator, or another privileged caller with permission to test model connections, could cause LiteLLM to read files from the local filesystem via an oidc/file/ reference.
Because exploitation requires privileged proxy access, this is treated as a defense-in-depth issue rather than a cross-tenant privilege bypass.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The issue is fixed in 1.83.10-stable.
LiteLLM recommend upgrading to 1.83.10-stable or later.
Frequently Asked Questions
- What is CVE-2026-59819? CVE-2026-59819 is a low-severity security vulnerability in litellm (pip), affecting versions < 1.83.10. It is fixed in 1.83.10.
- Which versions of litellm are affected by CVE-2026-59819? litellm (pip) versions < 1.83.10 is affected.
- Is there a fix for CVE-2026-59819? Yes. CVE-2026-59819 is fixed in 1.83.10. Upgrade to this version or later.
- Is CVE-2026-59819 exploitable, and should I be worried? Whether CVE-2026-59819 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-59819 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-59819? Upgrade
litellmto 1.83.10 or later.