Defined in 2 files
Last patched
apply_guardrail in BerriAI/litellm was changed by 1 published CVE fixes in 2026, in 2 distinct patches that added or removed 21 lines in total.
The name occurs in 2 files: litellm/proxy/guardrails/guardrail_hooks/custom_code/custom_code_guardrail.py, litellm/proxy/guardrails/guardrail_endpoints.py.
BerriAI/litellm has 22 CVEs with a located fix in total, so 5% of them touched this function.
Every published CVE whose fix changed apply_guardrail, newest first, with the lines each fix touched.
CVE-2026-59821 · litellm/proxy/guardrails/guardrail_endpoints.py · lines 1633–1636 · +4 −4
CVE-2026-59821 · litellm/proxy/guardrails/guardrail_hooks/custom_code/custom_code_guardrail.py · lines 44–56 · +7 −6
Get an alert when the next CVE fix lands in BerriAI/litellm, with the patched functions.
Monitor litellm CVEsFunctions in the same files that CVE fixes also changed.
Functions in BerriAI/litellm changed by the most CVE fixes.
Common questions about CVE fixes to apply_guardrail.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.
