Next.js
Next.js: Server-Side Request Forgery in Image Optimization
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 that matches images.remotePatterns, allowing the optimized image fetch to reach private IP addresses after the URL passes the allow-list check. Applications without images.remotePatterns are not affected. Administrators unable to upgrade should audit allow-listed hosts and avoid entries whose DNS records are not trusted. This issue is fixed in version 16.3.8.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.3high · scored by CNA · CWE-918
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
vercel next.js
- >= 16.0.0, < 16.3.8
Fixed in 16.3.8
Mitigation
Upgrade next.js to 16.3.8 or later.
References
- Vendor advisory github.com/vercel/next.js/security/advisories/…
- Patch github.com/vercel/next.js/commit/e002ad68bd676…
- Release notes github.com/vercel/next.js/releases/tag/v16.3.8
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.