CVE-2026-110719

Deferred Deferred - Pending Action

Portkey AI Gateway SSRF via Untrusted Custom Host Header

Publication date: 2026-10-14

Last updated on: 2026-10-16

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-14

Last Modified

2026-10-16

Generated

2026-10-19

AI Q&A

2026-10-15

EPSS Evaluated

2026-10-18

NVD

CVE-2026-110719

EUVD

EUVD-2026-101142

Affected Vendors & Products

Vendor	Product	Version / Range
Portkey-AI	gateway	1.14.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-918	The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

Executive Summary

This is an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in Portkey AI Gateway versions 1.14.0 through 1.15.2. It allows attackers to send crafted requests with a malicious x-portkey-custom-host header to reach internal loopback or Docker host services. The gateway trusts localhost-style hosts by default, bypassing security checks and relaying responses from internal services to the attacker.

Detection Guidance

Check if Portkey AI Gateway versions 1.14.0 through 1.15.2 are running by inspecting the version or deployment logs. Monitor network traffic for requests to localhost, Docker host services, or internal IPs via the /v1 endpoint with the x-portkey-custom-host header. Review logs for suspicious outbound connections to loopback addresses or Docker services.

Impact Analysis

Unauthenticated attackers can access sensitive internal services like admin panels or APIs not meant for external exposure. They can send requests to loopback addresses or Docker hosts and receive responses, potentially exposing confidential data or internal system details. The impact is limited to default-trusted destinations but can still compromise confidentiality.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. Exposure of internal services or data may result in non-compliance with data protection regulations, potentially leading to legal penalties or reputational damage.

Mitigation Strategies

Upgrade to a patched version of Portkey AI Gateway beyond 1.15.2. Disable or restrict the x-portkey-custom-host header if not required. Configure TRUSTED_CUSTOM_HOSTS to explicitly allow only necessary hosts. Ensure /v1 routes require authentication. Block loopback and Docker host IPs in firewall rules.

Hi! I’m here to help you understand CVE-2026-110719. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70