CVE-2026-59819
Description
A flaw was found in LiteLLM, a proxy server for Large Language Model (LLM) APIs. A privileged caller, such as a proxy administrator, with permissions to test model connections, could exploit the /health/test_connection endpoint. By supplying specific environment or OIDC (OpenID Connect) file references, an attacker could read arbitrary files from the local filesystem. This unauthorized file access could lead to information disclosure.
Statement
LiteLLM Proxy Server exposes a POST /health/test_connection endpoint that resolves os.environ/ references supplied in request parameters and reads OIDC credential files via the oidc/file/ secret provider without restricting the file path to an approved credentials directory. A caller with access to this endpoint could read local environment variable values or arbitrary files reachable via a crafted OIDC file reference, resulting in information disclosure. This is fixed upstream in litellm 1.83.14, which rejects os.environ/ references in request parameters and enforces an allow-listed OIDC credential directory. Red Hat components that use the litellm Python package only as an LLM client library (litellm.completion()/litellm.acompletion() and similar), without running the LiteLLM Proxy Server, do not expose this endpoint and are not affected.
Mitigation
Upgrade to litellm >= 1.83.14. If upgrading is not immediately possible, restrict network access to the LiteLLM Proxy Server administrative API (including /health/test_connection) to trusted, authenticated proxy/team administrators only, and avoid setting LITELLM_OIDC_ALLOWED_CREDENTIAL_DIRS or OIDC file secret providers to sensitive filesystem paths.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.9 | 4.9 | N/A |
| Attack Vector | Network | Network | N/A |
| Attack Complexity | Low | Low | N/A |
| Privileges Required | High | High | N/A |
| User Interaction | None | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | High | High | N/A |
| Integrity Impact | None | None | N/A |
| Availability Impact | None | None | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
NVD: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
