LiteLLM v1.100.0 ships two credential-leak fixes: virtual keys forwarded to Google, and provider secrets copied into spend logs
LiteLLM's v1.100.0 stable release on 2026-09-06 at 05:33 UTC carries PR #38114, which stopped credential-less Vertex passthrough from forwarding every proxy auth header (Authorization, x-litellm-api-key, x-goog-api-key, api-key, x-api-key, Ocp-Apim-Subscription-Key and the operator-configured key header) upstream to Google, meaning the caller's LiteLLM virtual key reached a third party. It also carries #38133, which scrubs forwarded Authorization headers and provider credentials out of the retry/fallback breadcrumb that is explicitly routed to spend logs and logging callbacks. Anyone running LiteLLM as a shared gateway with Vertex passthrough should treat previously-issued virtual keys as exposed to Google's request logs.
Source
↳ Follow the thread