What is CVE-2026-59823?

CVE-2026-59823 is a medium-severity server-side request forgery (SSRF) vulnerability in litellm (pip), affecting versions <= 1.83.8. It is fixed in 1.83.9. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

Which versions of litellm are affected by CVE-2026-59823?

litellm (pip) versions <= 1.83.8 is affected.

Is there a fix for CVE-2026-59823?

Yes. CVE-2026-59823 is fixed in 1.83.9. Upgrade to this version or later.

Is CVE-2026-59823 exploitable, and should I be worried?

Whether CVE-2026-59823 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.

What actually determines whether CVE-2026-59823 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-59823?

Upgrade litellm to 1.83.9 or later.

CVE-2026-59823 in litellm

Q: Which versions of litellm are affected by CVE-2026-59823?

litellm (pip) versions <= 1.83.8 is affected.

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

Yes. CVE-2026-59823 is fixed in 1.83.9. Upgrade to this version or later.

Q: Is CVE-2026-59823 exploitable, and should I be worried?

Whether CVE-2026-59823 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.

Q: What actually determines whether CVE-2026-59823 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.

Q: How do I fix CVE-2026-59823?

Upgrade litellm to 1.83.9 or later.

Summary

LiteLLM Proxy has server-side request forgery via the user_config request parameter

A server-side request forgery in LiteLLM Proxy lets an authenticated caller redirect the
proxy's outbound request to a host of their choosing by smuggling an api_base inside the
user_config request body, bypassing the existing parameter guard.

Details

LiteLLM Proxy validates request bodies with is_request_body_safe, which blocks the
api_base and base_url parameters but does not cover user_config. The user_config
object is used to build the outbound router for a request, so a caller can place an
api_base inside it and reach an arbitrary host. The guard only inspected the two
top-level keys, so the same api_base nested inside user_config was never checked.

Exploitation requires a valid virtual key.

Affected / Patched

Affected: <= 1.83.8
Patched: 1.83.9

Impact

An authenticated caller can make the proxy issue server-side requests to internal or
external hosts of their choosing, reaching endpoints the caller cannot otherwise access.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

Affected versions

litellm (<= 1.83.8)

Security releases

litellm → 1.83.9 (pip)

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 environment New to Kodem? Get a demo →

Remediation advice

Upgrade to 1.83.9 or later (released 2026-04-17).

Frequently Asked Questions

What is CVE-2026-59823? CVE-2026-59823 is a medium-severity server-side request forgery (SSRF) vulnerability in litellm (pip), affecting versions <= 1.83.8. It is fixed in 1.83.9. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
Which versions of litellm are affected by CVE-2026-59823? litellm (pip) versions <= 1.83.8 is affected.
Is there a fix for CVE-2026-59823? Yes. CVE-2026-59823 is fixed in 1.83.9. Upgrade to this version or later.
Is CVE-2026-59823 exploitable, and should I be worried? Whether CVE-2026-59823 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-59823 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-59823? Upgrade litellm to 1.83.9 or later.