AI Stack Alert High For CISO, SOC / IR, AppSec, AI Eng AI-assisted
LiteLLM < 1.95.0: authenticated file read via vertex_ai_credentials alias
LiteLLM proxy versions before 1.95.0 let an authenticated user read arbitrary local files through /utils/transform_request by sending a crafted vertex_ai_credentials value. The request-body blocklist covered vertex_credentials but missed this alias, so the value reached the Vertex AI credential loader. Fixed in 1.95.0.
Why it matters
A user with only the internal_user_viewer role, which can be obtained through SSO on many deployments, can read files the proxy process can read. Reading /proc/self/environ can expose LITELLM_MASTER_KEY and provider API keys, enabling full proxy-admin control.
Do this
- Upgrade LiteLLM to 1.95.0 or later.
- Until upgraded, review which users hold the internal_user_viewer role and any SSO auto-provisioning that grants it.
- Rotate LITELLM_MASTER_KEY and provider API keys if an affected version was exposed to untrusted users, since file reads may have exposed them.
- Review proxy logs for requests to /utils/transform_request that include vertex_ai_credentials.
Signals
- NoCISA KEV
- 8.1CVSS
- 37/100Priority
- 85%Confidence
Evidence
“The request-body safety blocklist rejected `vertex_credentials` but missed its alias `vertex_ai_credentials`”
“Upgrade to `1.95.0` or later. The fix adds the missing alias to the request-body blocklist”
Sources
Affected / related
LiteLLM proxy, arbitrary local file read
Published 2026-10-27 15:32 UTC · updated 2026-11-08 02:40 UTC · AI-assisted summary, checked against quoted sources · How we score