Is CVE-2026-59819 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-59819 being exploited in the wild.

How severe is CVE-2026-59819?

Medium severity, with a CVSS score of 4, published 8 July 2026.

Which products and versions are affected?

Berriai LiteLLM < 1.83.10-stable; litellm (PyPI) ECOSYSTEM:introduced=0,fixed=1.83.10.

Is there a fix for CVE-2026-59819?

Yes. litellm (PyPI): upgrade to 1.83.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-59819 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-59819?

Check whether you run Berriai LiteLLM or litellm (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-59819: BerriAI LiteLLM local file read in health test_connection endpoint

Q: Which products and versions are affected?

Berriai LiteLLM < 1.83.10-stable; litellm (PyPI) ECOSYSTEM:introduced=0,fixed=1.83.10.

Q: Is there a fix for CVE-2026-59819?

Yes. litellm (PyPI): upgrade to 1.83.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-59819 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-59819?

Check whether you run Berriai LiteLLM or litellm (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-59819 · Severity: medium · CVSS 4 · Published 2026-07-08

LiteLLM is a proxy server used to connect various AI models to applications. A security flaw in its connection testing tool allows an administrator to read sensitive files from the server's local storage. While this requires administrative access, it could allow a malicious insider or a compromised admin account to access configuration data or other system files.

Technologies: Berriai LiteLLM, litellm (PyPI). Vendors: Berriai, PyPI.

Quick answers

Is CVE-2026-59819 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-59819 being exploited in the wild.
How severe is CVE-2026-59819?: Medium severity, with a CVSS score of 4, published 8 July 2026.
Which products and versions are affected?: Berriai LiteLLM < 1.83.10-stable; litellm (PyPI) ECOSYSTEM:introduced=0,fixed=1.83.10.
Is there a fix for CVE-2026-59819?: Yes. litellm (PyPI): upgrade to 1.83.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-59819 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-59819?: Check whether you run Berriai LiteLLM or litellm (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

litellm (PyPI): upgrade to 1.83.10 or later
```
pip install "litellm>=1.83.10"
```

Technical details

A local file inclusion (LFI) vulnerability exists in LiteLLM's `/health/test_connection` endpoint due to improper validation of the `litellm_params` parameter. The endpoint resolves request-supplied OIDC file references (using the `oidc/file/` prefix), allowing an attacker to specify arbitrary local file paths. Exploitation requires high privileges (proxy administrator) and network access to the management endpoint. Successful exploitation allows the reading of local files, potentially exposing sensitive environment variables or system secrets. The issue is addressed in version 1.83.10-stable by improving how file references are resolved.

Affected products

BerriAI LiteLLM < 1.83.10-stable

Identifiers

CVE-2026-59819
GHSA-4g5m-c9r5-49xf
PYSEC-2026-3476

Timeline

2026-06-30: disclosed: Initial report to vendor
2026-07-08: advisory: NVD publication
2026-07-22: patched: GitHub Advisory published and fix confirmed in 1.83.10-stable

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.