CVE-2026-110719

7.2High

Published 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

7.2High

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Impact: Limited impact
Weakness: CWE-918

Impact

Unauthenticated remote attackers can make the gateway send HTTP requests to loopback and internal Docker host services and read the responses. All they need is network access to the gateway's /v1 endpoints.

Root cause

The isValidCustomHost validation function incorrectly trusts localhost-style target addresses when the TRUSTED_CUSTOM_HOSTS configuration option is not set.

Affected systems

Portkey AI Gateway 1.14.0 through 1.15.2

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Fix & remediation

Upgrade to a version past 1.15.2 once available. As an immediate mitigation, explicitly define the TRUSTED_CUSTOM_HOSTS environment variable to an allowlist of approved domains or a dummy domain to disable fallback to localhost.

shell

$ docker run -e TRUSTED_CUSTOM_HOSTS="api.example.com" portkeyai/gateway:latest

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

Portkey AI Gateway 1.14.0 through 1.15.2 contains a server-side request forgery vulnerability that allows unauthenticated attackers to reach loopback and Docker host services because isValidCustomHost trusts localhost-style hosts when TRUSTED_CUSTOM_HOSTS is unset. Attackers can send /v1 requests with a crafted x-portkey-custom-host header, such as via the ollama provider, to make the gateway call internal services and return their responses.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-110719