LiteLLM versions prior to 1.83.0 with JWT authentication enabled are vulnerable to an authentication bypass due to OIDC userinfo cache key collisions. The cache key uses only the first 20 characters of the JWT token, which can be identical for different tokens signed with the same algorithm. An attacker can exploit this to impersonate legitimate users by crafting tokens with matching cache keys. This vulnerability is fixed in version 1.83.0 by using the full hash of the JWT token as the cache key. The vulnerability has a critical severity with a CVSS score of 9.4. Most instances are not affected as JWT authentication is not enabled by default.