GHSA-72m8-9m7m-h278
Fix: BerriAI/litellm@e50b448GHSA-72m8-9m7m-h278 is a Code Injection vulnerability in litellm. O3 Security confirms whether GHSA-72m8-9m7m-h278 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
LiteLLM: Custom Code Guardrails production endpoints bypass code safety checks
Real-World Exposure
litellmReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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:
- Restrict access to
POST /guardrailsandPUT /guardrails/{guardrail_id}to trusted administrators only. - Ensure
LITELLM_MASTER_KEYis configured. - Avoid enabling Custom Code Guardrails for untrusted users.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | litellm | all versions | 1.82.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for litellm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update litellm to 1.82.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-72m8-9m7m-h278 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-72m8-9m7m-h278 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-72m8-9m7m-h278. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-72m8-9m7m-h278 in your dependencies?
O3 detects GHSA-72m8-9m7m-h278 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.