Skip to main content
VulnerabilityPublished

CVE-2025-66405: Portkey.ai Gateway · Server-Side Request Forgery (SSRF) in Custom Host

Affects @portkey-ai/gatewaySource GCVE Database

0
Compare
Authoritative record:CVE-2025-66405· Medium 6.9

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

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
npm@portkey-ai/gatewayAffected
  • <1.14.0
Fixed in
  • 1.14.0

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

Community reviews

Loading reviews…