Security brief

LiteLLM guardrail creation paths lacked the checks applied in testing

REVIEW

CVE-2026-59821 concerned custom Python guardrails and administrative access, with additional risk when no master key was configured.

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

What happened

LiteLLM’s advisory describes inconsistent validation between Custom Code Guardrails testing and production create or update paths. A user permitted to manage guardrails could submit Python that executed in the proxy environment.

The advisory also warns that deployments without a master key could treat callers as administrators. The access prerequisites matter; this should not be described as unrestricted unauthenticated execution across every installation.

The project lists 1.82.0-stable as fixed. Upgrade to a maintained release, configure the master key and restrict custom guardrail management to trusted administrators. Review process-accessible secrets if unauthorized guardrail code may have executed.

Read the original source.

Next step

Update LiteLLM, configure authentication and restrict custom guardrail administration.

What we know

Reported fix: 1.82.0-stable.

What remains unknown

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

Source references

GIT

github.com LiteLLM guardrail creation paths lacked the checks applied in testing

Technical details

CVE: CVE-2026-59821