Portkey AI Gateway accepts a user-controlled x-portkey-custom-host header and uses it as the base URL for provider requests. When TRUSTED_CUSTOM_HOSTS is unset, isValidCustomHost trusts localhost, 127.0.0.1, ::1, host.docker.internal, and *.localhost; this trusted-host path returns success before private-IP and metadata checks are applied. The /v1/* routes invoke requestValidator, after which the provider context builds a URL from the custom host and passes the request through the gateway's fetch path. The Ollama provider does not require an API key for this path, so a remote unauthenticated attacker can cause the gateway to contact loopback or Docker-host services and relay their responses. The demonstrated scope centers on the default-trusted destinations; the public analysis does not claim RCE or unrestricted access to every internal network.