Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-82270 – Server-Side Request Forgery (SSRF) – Portkey AI Gateway 1.14.0–1.15.2

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82270 is a server-side request forgery (SSRF) vulnerability in Portkey AI Gateway, an open-source AI gateway/proxy used to route requests to LLM providers. The flaw lies in the /v1/proxy/* route, which lacks the requestValidator middleware that validates destination hosts elsewhere in the gateway. It carries a CVSS score of 8.7 (high severity) and can allow an attacker to force the gateway to send authenticated requests to internal or arbitrary network destinations.

Technical details

  • Root cause: The /v1/proxy/* route does not enforce the requestValidator middleware that normally restricts the destination host for outbound requests made by the gateway.
  • Trigger condition: An attacker sends a request to the proxy route while setting the x-portkey-custom-host header to an internal address (e.g., a cloud metadata endpoint or internal service) or an otherwise attacker-controlled host.
  • Attack vector: Network — no authentication to the internal target and no user interaction are required beyond reaching the exposed gateway endpoint.
  • Impact: The gateway forwards the request — including the Authorization header — to the attacker-specified host, allowing internal services to be reached and provider API keys/credentials to be exfiltrated to a host of the attacker’s choosing.

Affected software

  • Portkey AI Gateway (@portkey-ai/gateway), versions 1.14.0 through 1.15.2 (inclusive)

Severity

  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0 Base Score: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Portkey AI Gateway to a version beyond 1.15.2 that enforces the requestValidator middleware (including allow-listing of trusted hosts) on the /v1/proxy/* route.
  • If no patch is available yet: Restrict or disable the /v1/proxy/* route at the network/reverse-proxy layer, block or strip the x-portkey-custom-host header from external clients, and block outbound gateway traffic to internal ranges and cloud metadata addresses (e.g., 169.254.169.254, 127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).
  • Rotate any provider API keys/credentials that may have transited the gateway prior to remediation.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw HTTP response body: AI Gateway says hey!

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge