Security brief

LiteLLM routing overrides could send stored provider credentials to another destination

REVIEW

CVE-2026-84377 affected authenticated requests and has separate fixed releases across several supported branches.

Published 29 Oct 2026 · Material update 30 Sep 2026 — last time the underlying evidence changed · Evidence: high

What happened

LiteLLM’s advisory describes incomplete validation of request-body routing parameters. An authenticated caller could redirect a provider request to another destination while the proxy still attached configured credentials, enabling secret exposure and server-side request forgery.

The issue affects the gateway’s request handling. Provider names in the configured credentials are not evidence that those providers’ own systems were breached.

The advisory lists branch fixes from 1.88.6 through 1.96.2, including 1.95.1 and 1.94.3. Match your branch to the full advisory, use a maintained release and disable client-side credential overrides where appropriate. Investigate credential use if untrusted callers reached an affected proxy.

Read the original source.

Next step

Apply the fix for your branch and restrict client-side routing and credential overrides.

What remains unknown

Open question
The sources reviewed do not establish whether your deployment was exploited.

Source references

Technical details

CVE
CVE-2026-84377