CVE-2025-66405: Portkey.ai Gateway · Server-Side Request Forgery (SSRF) in Custom Host
Affects @portkey-ai/gatewaySource GCVE Database
Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.14.0 when convenient.
Data as of 21 Nov 2026, 03:47 UTC
- Patch
- Available – fixed in 1.14.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade @portkey-ai/gateway to 1.14.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@portkey-ai/gateway | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Portkey.ai Gateway to version 1.14.0 or later, where the vulnerability is patched. The fix includes strict validation of the x-portkey-custom-host header and blocks requests to non-routable, loopback, private, and metadata IP addresses. No additional mitigation is required if the system is updated to this version.
Description
Portkey.ai Gateway versions prior to 1.14.0 contain a Server-Side Request Forgery (SSRF) vulnerability via the x-portkey-custom-host request header. This header is used to determine the destination baseURL for proxy requests without sufficient validation, allowing attackers to make the server perform arbitrary requests. The vulnerability enables potential access to internal network resources, including sensitive endpoints like AWS metadata services. The issue is fixed in version 1.14.0 by implementing strict allow-list validation and blocking requests to non-routable, loopback, private, and metadata IP addresses.
References
- github.com/Portkey-AI/gateway/security/advisories/GHSA-hhh5-2cvx-vmfp (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2025-66405 (opens in a new tab)
- github.com/Portkey-AI/gateway/pull/1372 (opens in a new tab)
- github.com/Portkey-AI/gateway/commit/b5a7825ba5f4e6918deb32d9969899ce2229a885 (opens in a new tab)
- github.com/Portkey-AI/gateway (opens in a new tab)