Antthelimey

Deployments using the nondefault HTTP transport with authentication enabled incorrectly use the leftmost caller-supplied `X-Forwarded-For` value as the client address for login rate limiting. The `ExtractIPAddress` function in `internal/auth/middleware.go` passes this value to the `IsAllowed()` and `RecordFailedAttempt()` functions in `internal/auth/rate limiter.go`. This allows an unauthenticated user to bypass throttling by rotating addresses or to exhaust the rate limit bucket of another user by spoofing their address. This issue is facilitated by the published nginx configuration, which appends rather than replaces the `X-Forwarded-For` header.

The unauthenticated query API in internal/server/handlers.go returns error messages from failed LLM provider calls. These responses can include provider-controlled text that quotes a partially masked API key. A remote caller can trigger an authentication failure to obtain a portion of the operator's credentials for the third-party provider account via the query API error response.