← Back
CVE-2026-82270
high
CVSS 7.5
SSRF (Server-Side Request Forgery) in CVE-2026-82270 (CVE-2026-82270)
Summary
SSRF in CVE-2026-82270 (CVE-2026-82270). Confidential information can be exposed externally. Exploitable via `Authorization header`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-82270** has been found in CVE-2026-82270.
Attackers can target a specific entry point like `Authorization header` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-82270 CVE-2026-82270" on the vendor's site.
CVE-2026-82270 (CVE-2026-82270) — CWE-918 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Authorization header / Host header
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SSRF** (CWE-918) exists in CVE-2026-82270. Attackers reach the vulnerable code path via `Authorization header` without authentication.
📍 Affected scope
CVE-2026-82270 — . Attack surface: Authorization header / Host header.
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.依存マニフェストで影響コンポーネントを特定する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- web https://github.com/Portkey-AI/gateway
- web https://github.com/Portkey-AI/gateway/blob/669825cbe89ee51569918b8f78a9db486fd69dd4/src/index.ts
- web https://github.com/Portkey-AI/gateway/issues/1718
- web https://www.vulncheck.com/advisories/portkey-ai-gateway-server-side-request-forgery-via-v1-proxy
- web https://nvd.nist.gov/vuln/detail/CVE-2026-82270
- web https://github.com/advisories/GHSA-rv66-rgwx-xfrj