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. Source Code Location: https://github.com/vercel/next.js Affected Packages: - npm:next, affected >= 16.0.0, < 16.3.8, patched in 16.3.8 CWEs: - CWE-918: Server-Side Request Forgery (SSRF) CVSS: - Primary: score 6.5, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N - CVSS_V4: score 8.3, CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N - CVSS_V3: score 6.5, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N References: - 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 - https://github.com/advisories/GHSA-cjq9-62q9-8jv4