LiteLLM· ()

Patch todayVendor security release

LiteLLM security releases: 1.84.0, 1.83.10-stable, 1.83.7-stable, 1.82.0-stable

What
LiteLLM published security fixes. Upgrade to 1.84.0 / 1.83.10-stable / 1.83.7-stable / 1.82.0-stable (whichever matches your branch). Fixes 4 CVEs. Vendor severity: Low, High, Medium.
Fix
Upgrade to 1.84.01.83.10-stable1.83.7-stable1.82.0-stable
Why this tier
CVE-2026-59822: Known exploited server software, exploitation is automatable.
Exploited
Yes: 1 CVE in CISA KEV · highest EPSS 0.9%
Share this

What to do now#

  1. Check whether you run an affected LiteLLM version:
    pip show litellm | grep Version
  2. Upgrade to the fixed release for your branch: 1.84.0, 1.83.10-stable, 1.83.7-stable, 1.82.0-stable.Vendor announcement
  3. Upgrade the LiteLLM proxy image or package and restart; rotate any keys the proxy held if the advisory involves key exposure.
  4. Using distro packages? Distros backport fixes under their own version numbers. Check your distro's status for CVE-2026-59819 (and the other 3 CVEs):Debian · Ubuntu · Red Hat · Alpine
  5. This is exploited in the wild: after patching, check exposed systems for signs of compromise.

CVEs 4#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-59822Patch today8.8 (v4.0)0.8%Yesactive
CVE-2026-59820Routine6.1 (v4.0)0.6%Nonone
CVE-2026-59819Routine2.1 (v4.0)0.6%Nonone
CVE-2026-59821Routine2.1 (v4.0)0.9%Nonone

Sources#

Built from LiteLLM: GitHub Security Advisories (BerriAI/litellm), checked . Tier from the published rubric.

Also on today's list

See today's list → · Coming up →

Something wrong on this page?
Anonymous. Reports are checked against the primary source.