LiteLLM proxy configuration update let lower-privileged users reach admin effects

A lower-privileged LiteLLM user with legitimate access could submit a proxy configuration change reserved for administrators. Check Point traced how that boundary failure exposed file paths and service credentials and could cause attacker-supplied Python to be loaded by the server. The impact depends on reachable settings and valid lower-privilege authentication, not an unauthenticated HTTP endpoint.

The necessary foothold is an authenticated lower-privilege proxy user. The dangerous crossing happens when configuration controlled by that principal is processed with the proxy service’s file and module-loading authority; an unauthenticated remote exploit is not what the record shows.