Next.js has Server-Side Request Forgery in Image Optimization
## 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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-94483US | medium6.5 | — | ||
Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, Image Optimization can follow attacker-controlled DNS resolution for a remote URL t… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/vercel/next.jsPACKAGE
- https://github.com/vercel/next.js/commit/e002ad68bd676bb0ed0c87bb22e3590304763e0bWEB
- https://github.com/vercel/next.js/releases/tag/v16.3.8WEB
- https://github.com/vercel/next.js/security/advisories/GHSA-cjq9-62q9-8jv4WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-94483ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan