# CVE-2026-82270: Portkey AI Gateway Server-Side Request Forgery via /v1/proxy/*

> Attackers can exploit SSRF in Portkey AI Gateway to access internal services and exfiltrate API keys via the proxy route.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-rv66-rgwx-xfrj

## What is CVE-2026-82270?

CVE-2026-82270 is a high-severity server-side request forgery vulnerability in Portkey-AI gateway, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Portkey AI Gateway through 1.15.2 contains a server-side request forgery vulnerability in the /v1/proxy/* route that lacks requestValidator middleware. Attackers can set the x-portkey-custom-host header to internal addresses and forward requests with Authorization headers to reach internal services and exfiltrate provider API keys.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-82270?


## How do I fix CVE-2026-82270?

No fix has been published for CVE-2026-82270 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82270 being exploited?

There is no known exploitation of CVE-2026-82270 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82270 and fix it if it is affected.

What it is: CVE-2026-82270 is a high-severity server-side request forgery vulnerability in Portkey-AI gateway, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82270 in the wild and no public exploit code.

Affected product: Portkey-AI gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82270/ (Markdown: https://insights.sbomify.com/CVE-2026-82270/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82270
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82270
- OSV: https://osv.dev/vulnerability/CVE-2026-82270

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82270/
Summaries are generated and may contain mistakes; the official description above is the record.