VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

litellm: vulnerability history, versions and safety

litellm is a package in the PyPI ecosystem. Vulert records 83 vulnerabilities for it across 120 releases, from Apr 2024 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
83 vulnerabilities recorded C8 H18 M8 L9 U40
i
27 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
69 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in PyPI →

See all litellm vulnerabilities

Vulert verdict on litellm 1.107.0.dev3 i

Updated on 23 Oct 2026

Careful: 1.107.0.dev3 was published with malicious code in it, not just a bug. Do not install it.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Niche
  • Community Active

The current release contains malicious code, which caps this score.

What to do: Do not resolve 1.107.0.dev3 as-is. Check whether you already run an affected release and pin a version the maintainers have re-published. Check what you run: Vulert alerts you when a safe version is published. Monitor it with Vulert →

  • Current release 1.107.0.dev3 — affected i
  • Vulnerabilities on record 83 over 2 years · 69 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 27 i
  • Malicious packages 1 i
  • Stars 61,716 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for litellm, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.106.2 21 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.105.3 21 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.103.7 21 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.104.5 21 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.106.1 20 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.105.2 20 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.103.6 20 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.107.0rc2 20 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.104.4 20 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.107.0rc1 18 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.106.0 18 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.103.5 17 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.107.0.dev3 16 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.106.0rc4 15 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.107.0.dev2 15 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.106.0rc3 14 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.107.0.dev1 14 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.105.1 14 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.106.0rc2 13 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.104.3 11 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.105.0 11 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.106.0rc1 11 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.106.0.dev3 09 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.105.0rc3 08 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.104.2 08 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.102.4 08 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.101.6 08 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.106.0.dev2 08 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.105.0rc2 07 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.104.1 07 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.103.4 07 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.102.3 07 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.100.5 07 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.101.5 07 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.106.0.dev1 07 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.105.0rc1 04 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.103.3 03 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.104.0 03 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.105.0.dev2 02 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.103.2 01 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.101.4 01 Oct 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.105.0.dev1 30 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.104.0rc2 30 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.103.1 29 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.102.2 29 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.101.3 29 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.100.4 29 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.104.0rc1 28 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.103.0 27 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.104.0.dev2 25 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.100.3 25 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.99.4 25 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.98.1 25 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.101.2 24 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.99.3 23 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.102.1 23 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.101.1 23 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.100.2 23 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.99.2 23 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.104.0.dev1 23 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.103.0rc1 20 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.102.0 20 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.103.0.dev2 18 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.102.0rc2 16 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.103.0.dev1 16 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.101.0 14 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.102.0rc1 13 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.102.0.dev2 11 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.101.0rc2 10 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.100.1 10 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.102.0.dev1 09 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.101.0rc1 06 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.100.0 06 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.101.0.dev2 03 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.101.0.dev1 01 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.99.0 01 Sep 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.99.0rc2 30 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.100.0rc1 30 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.100.0.dev2 28 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.100.0.dev1 26 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.99.0rc1 23 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.98.0 22 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.99.0.dev2 21 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.99.0.dev1 19 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.98.0rc1 16 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.97.0 16 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.98.0.dev2 13 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.98.0.dev1 12 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.96.2 11 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.95.1 09 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.94.3 09 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.93.2 09 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.92.2 09 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.91.5 09 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.90.7 09 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.96.0 09 Aug 2026 U1 MIT Yes Details →
1.89.7 09 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.88.6 09 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.97.0rc1 08 Aug 2026 C2 H3 M2 L7 U13 malicious MIT No Details →
1.94.2 08 Aug 2026 U1 MIT Yes Details →
1.97.0.dev1 05 Aug 2026 C2 H3 M2 L7 U13 malicious — No Details →
1.96.0rc1 03 Aug 2026 C2 H3 M2 L7 U13 malicious — No Details →
1.95.0 02 Aug 2026 U1 — Yes Details →
1.95.0rc3 01 Aug 2026 C2 H3 M2 L7 U13 malicious — No Details →
1.96.0.dev2 31 Jul 2026 C2 H3 M2 L7 U13 malicious — No Details →
1.95.0rc2 31 Jul 2026 C2 H3 M2 L7 U13 malicious — No Details →
1.94.1 30 Jul 2026 U1 — Yes Details →
1.95.0rc1 29 Jul 2026 C2 H3 M2 L7 U13 malicious — No Details →
1.93.1 29 Jul 2026 U1 — Yes Details →
1.94.0 28 Jul 2026 U1 — Yes Details →
1.95.0.dev3 24 Jul 2026 C2 H3 M2 L7 U13 malicious — No Details →
1.94.0rc3 22 Jul 2026 C2 H3 M2 L7 U13 malicious — No Details →
1.94.0rc2 20 Jul 2026 C2 H3 M2 L7 U13 malicious — No Details →
1.92.1 19 Jul 2026 U1 — Yes Details →
1.93.0 19 Jul 2026 U1 — Yes Details →
1.91.4 19 Jul 2026 U1 — Yes Details →
1.90.6 19 Jul 2026 U1 — Yes Details →
1.94.0rc1 18 Jul 2026 C2 H3 M2 L7 U13 malicious — No Details →
1.94.0.dev3 17 Jul 2026 C2 H3 M2 L7 U13 malicious — No Details →
1.90.5 16 Jul 2026 U1 — Yes Details →

The newest 120 of 948 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 8
  • 2025 6
  • 2026 69

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 69 of the 83 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for litellm

The 5 most severe of 83 vulnerabilities recorded for this package

Search all 83 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-37004: LiteLLM Server-Side Template Injection Vulnerability 9.8 critical 1.83.7 10 Sep 2026
CVE-2024-2952: LiteLLM Server-Side Template Injection Vulnerability 9.8 critical 1.34.42 29 Jun 2026
CVE-2026-37004: LiteLLM Server-Side Template Injection Vulnerability in /prompts/test Endpoint 9.8 critical 1.83.7 27 Aug 2026
CVE-2024-5751: litellm Remote Code Execution Vulnerability Due to Unsafe eval Usage 9.8 critical 1.40.16 29 Jun 2026
Remote Code Execution Vulnerability in litellm 9.8 critical 1.40.16 27 Jun 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About litellm

Is litellm safe to use?

Vulert records 83 vulnerabilities for litellm in PyPI: 8 critical, 18 high, 8 medium and 9 low, plus 40 not yet rated. 27 of them have no published fix yet, so those are the ones to avoid or mitigate. 1 are malicious-package vulnerabilities: the published package itself contained hostile code, not only a bug.

What is litellm's Vulert package health score?

Vulert scores litellm 15/100, which reads as critical. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release contains malicious code, which caps this score.

Is the latest version of litellm affected?

Yes. 1.107.0.dev3, the version you would install today, has 27 known vulnerabilities, and 27 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of litellm should I use?

1.107.0.dev3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does litellm have?

83 vulnerabilities are recorded for litellm in the PyPI ecosystem: 8 critical, 18 high, 8 medium and 9 low, plus 40 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new litellm vulnerabilities disclosed?

69 vulnerabilities were recorded for litellm in the last 12 months, and the oldest entry in this database dates to 10 Apr 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of litellm are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor litellm for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the litellm version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.