Next.js is a React framework for building full-stack web applications. In versions 15.5.0 through 15.5.20 and 16.0.0 through 16.2.10, when self-hosting Next.js with the default image loader, the Image Optimization API can optimize remotely hosted images if configured (not enabled by default). If those images contain malicious content, they can cause CPU exhaustion in /_next/image endpoints.Only config.images.remotePatterns is affected, and just the patterns in that array, whereas config.images.unoptimized: true, config.images.loader: 'custom', and Vercel are not impacted.
This issue has been fixed in versions 15.5.21 and 16.2.11.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
Present
Additional conditions required
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
None
No data modification
Availability
Low
Partial disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products 2
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Vercel Next.Js
cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
|
15.5.0
|
15.5.21
|
|
Vercel Next.Js
cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
|
16.0.0
|
16.2.11
|
References 5
https://github.com/vercel/next.js/security/advisories/GHSA-q8wf-6r8g-63ch
https://github.com/vercel/next.js/security/advisories/GHSA-q8wf-6r8g-63ch
https://github.com/vercel/next.js/pull/96006
https://github.com/vercel/next.js/pull/96006
https://github.com/vercel/next.js/commit/93cb90891402fa4c47798d03cb9e05c1323376…
https://github.com/vercel/next.js/commit/93cb90891402fa4c47798d03cb9e05c13233766c
https://github.com/vercel/next.js/releases/tag/v15.5.21
https://github.com/vercel/next.js/releases/tag/v15.5.21
https://github.com/vercel/next.js/releases/tag/v16.2.11
https://github.com/vercel/next.js/releases/tag/v16.2.11