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.
CVE-2026-82270
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (4)
Auto-updated Aug 28, 2026Portkey AI Gateway Server-Side Request Forgery via /v1/proxy/* | Advisories | VulnCheck
https://www.vulncheck.com/advisories/portkey-ai-gateway-server-side-request-forgery-via-v1-proxygateway/src/index.ts at 669825cbe89ee51569918b8f78a9db486fd69dd4 · Portkey-AI/gateway · GitHub
https://github.com/Portkey-AI/gateway/blob/669825cbe89ee51569918b8f78a9db486fd69dd4/src/index.tsGitHub - Portkey-AI/gateway: A blazing fast AI Gateway with integrated guardrails. Route to 1,600+ LLMs, 50+ AI Guardrails with 1 fast & friendly API. · GitHub
https://github.com/Portkey-AI/gatewaySSRF allowlist bypass and credential theft via /v1/proxy/* route -- @portkey-ai/gateway <= 1.15.2 · Issue #1718 · Portkey-AI/gateway · GitHub
https://github.com/Portkey-AI/gateway/issues/1718Vendor Advisories for CVE-2026-82270(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 06:13 UTCEG score recompute
- 2026-08-30 06:13 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 18:58 UTCGHSA enrichment
- 2026-08-29 07:42 UTCEG score recompute
- 2026-08-29 07:42 UTCGHSA enrichment
- 2026-08-28 20:26 UTCEG score recompute
- 2026-08-28 19:40 UTCEG score recompute
- 2026-08-28 19:36 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p91CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-82270?
When was CVE-2026-82270 disclosed?
Is CVE-2026-82270 actively exploited?
What is the CVSS score of CVE-2026-82270?
How do I remediate CVE-2026-82270?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82270
Is Your Infrastructure Affected by CVE-2026-82270?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.