An authentication bypass exists where the `get current user()` function in `gpustack/api/auth.py` incorrectly treats loopback request sources as the built-in administrator when `force auth localhost` is set to false. This occurs because the `client ip getter` function may accept a same-host reverse proxy peer or a client-supplied `X-GPUStack-Real-IP` loopback value, making remote requests appear to originate from 127.0.0.1. This flaw allows unauthenticated administrative access, enabling unauthorized user and model changes, the creation of persistent administrator API keys, and the disclosure of worker and cloud-provider secrets. Additionally, it allows remote code execution via the 'POST /v2/inference-backends/from-yaml' endpoint. Exploitation of this issue has been observed in the wild against a version 2.1.1 deployment.