Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-40217: LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /gu

60
This week
HIGH 8.8UPGRADE

CVE-2026-40217 is a high-severity flaw (CVSS 8.8) affecting litellm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.

Why this priority

  • High severity
  • EPSS top 3%: very likely to be exploited
  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance15.5% (top 3%)
CISA exploited listNo
WeaknessCWE-420, CWE-94
Published2026-04-10
Last modified2026-10-26
Publisher (CNA): MITRE · Vendor: litellm

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

litellm litellm UPGRADE
Affected: <= 2026-04-08
Fixed in: newer than 2026-04-08
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy litellm || rpm -q litellm || litellm --version
2. UPGRADE to newer than 2026-04-08 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade litellm
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade litellm
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Exact fixes by distribution

Python (pip) · litellm · FIXED · 1.83.10 · vulnerable: >= 1.81.8, < 1.83.10 · source
pip install --upgrade "litellm>=1.83.10" pip show litellm

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-40217?

litellm: upgrade to newer than 2026-04-08. Exact commands for each OS are on this page.

Is CVE-2026-40217 being exploited?

CVE-2026-40217 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-40217 affect?

CVE-2026-40217 affects litellm. Severity is high (CVSS 8.8). LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.

How urgent is CVE-2026-40217?

Priority 60/100. High severity; EPSS top 3%: very likely to be exploited; Public exploit reference

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.