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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/vercel/next.js/commit/93cb90891402fa4c47798d03cb9e05c13233766c Patch
- https://github.com/vercel/next.js/pull/96006 Issue Tracking, Patch
- https://github.com/vercel/next.js/security/advisories/GHSA-q8wf-6r8g-63ch Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.3 · vercelNVD modified 2026-10-24 13:10
Affected (CPE criteria) 1
cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
References 5
- https://github.com/vercel/next.js/commit/93cb90891402fa4c47798d03cb9e05c13233766c Patch
- https://github.com/vercel/next.js/pull/96006 Issue Tracking, Patch
- https://github.com/vercel/next.js/releases/tag/v15.5.21 Product, Release Notes
- https://github.com/vercel/next.js/releases/tag/v16.2.11 Product, Release Notes
- https://github.com/vercel/next.js/security/advisories/GHSA-q8wf-6r8g-63ch Vendor Advisory