Next.js: Denial of Service in the Image Optimization API using SVGs
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.3epss 0.5%
exploitation probability
0.5%top 59% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Affected products
vercel · next.jsReferences
https://github.com/vercel/next.js/commit/93cb90891402fa4c47798d03cb9e05c13233766chttps://github.com/vercel/next.js/pull/96006https://github.com/vercel/next.js/releases/tag/v15.5.21https://github.com/vercel/next.js/releases/tag/v16.2.11https://github.com/vercel/next.js/security/advisories/GHSA-q8wf-6r8g-63ch