Advisory

GHSA-72m8-9m7m-h278

Also known as: CVE-2026-59821, PYSEC-2026-3478

Summary

LiteLLM: Custom Code Guardrails production endpoints bypass code safety checks

Details

Impact

LiteLLM's Custom Code Guardrails production create/update paths did not apply the same sandboxing and validation used by the test endpoint.

A privileged user with access to create or update guardrails could submit custom Python code that executed in the LiteLLM proxy environment. In deployments without a configured master key, callers could be treated as proxy administrators, making this reachable without intended administrative authorization.

This could allow arbitrary code execution in the LiteLLM proxy container and exposure of secrets available to the process.

Patches

The issue is fixed in 1.82.0-stable.

LiteLLM recommend upgrading to 1.82.0-stable or later.

Workarounds

If upgrading is not immediately possible:

  1. Restrict access to POST /guardrails and PUT /guardrails/{guardrail_id} to trusted administrators only.
  2. Ensure LITELLM_MASTER_KEY is configured.
  3. Avoid enabling Custom Code Guardrails for untrusted users.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-07-22 22:38 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

litellm

PyPI · All systems

Affected

  • introduced 0, fixed 1.82.0 (ecosystem)

Fixed versions

1.82.0

Fix

  • Fixed version 1.82.0
    pip install --upgrade litellm==1.82.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences