LiteLLM Proxy: Three Exploited Flaws in CISA KEV
If you run a self-hosted LiteLLM Proxy older than 1.84.0, upgrade now and treat the provider keys it holds as possibly exposed; SDK-only users are not affected.
Must act: Operators of self-hosted LiteLLM Proxy (AI gateway) deployments, especially any reachable from the internet or from broad internal networks, and anyone still using the default sk-1234 master key.
Can relax: Projects that only import the litellm Python SDK as a client library and do not run the proxy server, and proxies already on 1.84.0 or later with a strong master key.
- Upgrade the proxy to 1.84.0 or later (pin an exact version and verify hashes or image digest).
- If you cannot upgrade, block /mcp/ and /mcp-rest/test/* at the reverse proxy and set general_settings.disable_error_logs: true.
- Replace any default master key (sk-1234) and never run the proxy without a master key.