Skip to content
Fencer Vulns
high 7.5

CVE-2024-6587 in the critical feed json

SSRF in berriai/litellm

published 2024-09-13 2 y ago modified 2026-09-10 1 mo ago also GHSA-g26j-5385-hhw3 , PYSEC-2026-1547 , EUVD-2024-2785

cvss
7.5
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
34.4%
EPSS 34.4% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known, plus a Nuclei check

Summary

A Server-Side Request Forgery (SSRF) vulnerability exists in berriai/litellm version 1.38.10. This vulnerability allows users to specify the `api_base` parameter when making requests to `POST /chat/completions`, causing the application to send the request to the domain specified by `api_base`. This request includes the OpenAI API key. A malicious user can set the `api_base` to their own domain and intercept the OpenAI API key, leading to unauthorized access and potential misuse of the API key.

Patch / fix

  • pypi litellm 1.44.8
  • berriai berriai/litellm 1.44.9
  • berriai litellm 1.44.9

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

34.38% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Nuclei template LiteLLM - Server-Side Request Forgery nuclei detection template
  • huntr.com https://huntr.com/bounties/4001e1a2-7b7a-4776-a3ae-e6692ec3d997 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OSV 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi litellm
<1.44.8
1.44.8

Affected products

  • berriai berriai/litellm
  • berriai litellm

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.