Local file read via unrestricted OIDC file references
Published Jul 8, 2026 · Updated Jul 8, 2026
File path control in LiteLLM before 1.83.10-stable allows remote authenticated users to read local files through the proxy. The /health/test_connection endpoint passes request-supplied litellm_params to get_secret(), which opens oidc/file/ paths without restricting them to credential directories. The caller must hold proxy-administrator privileges or equivalent permission to test model connections, and the consequence is limited to reading files accessible to the proxy process.
Summary
What happened
File path control in LiteLLM before 1.83.10-stable allows remote authenticated users to read local files through the proxy. The /health/test_connection endpoint passes request-supplied litellm_params to get_secret(), which opens oidc/file/ paths without restricting them to credential directories. The caller must hold proxy-administrator privileges or equivalent permission to test model connections, and the consequence is limited to reading files accessible to the proxy process.
The record
- CVE
- CVE-2026-59819
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- Berri AI
- Product
- LiteLLM
- Classifications
- CWE-73, T1005
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.83.10-stable
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo