Summary
Next.js has Server-Side Request Forgery in Image Optimization
Advisory details
Impact
An attacker-controlled, allow-listed remote URL can lead to server-side request forgery (e.g. to private IPs) during Image Optimization.
Workaround
Audit allow-listed remote URLs in images.remotePatterns (see https://nextjs.org/docs/app/getting-started/images#remote-images) for hosts that may not be trusted with their DNS entries. If no images.remotePatterns are configured, your app is not affected.
References
- https://github.com/advisories/GHSA-cjq9-62q9-8jv4
- https://github.com/vercel/next.js/security/advisories/GHSA-cjq9-62q9-8jv4
- https://nvd.nist.gov/vuln/detail/CVE-2026-94483
- https://github.com/vercel/next.js/commit/e002ad68bd676bb0ed0c87bb22e3590304763e0b
- https://github.com/vercel/next.js/releases/tag/v16.3.8
Related vulnerabilities
All Supply chain →- CRITICALCVE-2026-77524
KEDA: Privilege escalation from namespace admin to cluster admin via KEDA TriggerAuthentication
- MEDIUMGHSA-p3pr-8f3m-4qp8
pyLoad WindowsPhoneNotify addon: non-admin SETTINGS user triggers SSRF via unguarded http.client notification host
- MEDIUMCVE-2026-107394
Indico: Incomplete Server-Side Request Forgery (SSRF) check
- HIGHCVE-2026-60091
PraisonAI: Jobs API is unauthenticated by default and allows attacker-controlled webhook SSRF
- MEDIUMCVE-2026-107289
Pydantic AI: SSRF cloud-metadata blocklist bypass via IPv6 zone identifiers
- HIGHCVE-2026-61430
PraisonAI: DNS rebinding bypass in `web_crawl` SSRF protection allows internal response disclosure