Threat database

Portkey AI Gateway versions 1.14.0 through 1.15.2 have a server-side request forgery (SSRF) vulnerability. This flaw allows unauthenticated attackers to send specially crafted requests that cause the gateway to make internal network calls, including to loopback and Docker host services. The vulnerability arises because the isValidCustomHost function trusts localhost-style hosts when the TRUSTED_CUSTOM_HOSTS environment variable is not set. Attackers can exploit this by sending requests with a manipulated x-portkey-custom-host header, for example via the ollama provider, to retrieve responses from internal services.

Portkey AI Gateway through 1.15.2 contains a server-side request forgery vulnerability in the /v1/proxy/* route that lacks requestValidator middleware. Attackers can set the x-portkey-custom-host header to internal addresses and forward requests with Authorization headers to reach internal services and exfiltrate provider API keys.

Portkey.ai Gateway is a blazing fast AI Gateway with integrated guardrails. Prior to 1.14.0, the gateway determined the destination baseURL by prioritizing the value in the x-portkey-custom-host request header. The proxy route then appends the client-specified path to perform an external fetch. This can be maliciously used by users for SSRF attacks. This vulnerability is fixed in 1.14.0.