CVE-2026-64644
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).
Does this matter?
Lower severity and a low EPSS score (0.68%). Track it; it rarely justifies an emergency change on its own.
Description
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
- 6.3 MEDIUMCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M
- EPSS
- 0.68% probability · 50th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-407
- Affected
- vercel/next.js
- Source
- security-advisories@github.com
References
- https://github.com/vercel/next.js/commit/93cb90891402fa4c47798d03cb9e05c13233766cPatch
- https://github.com/vercel/next.js/pull/96006Issue Tracking, Patch
- https://github.com/vercel/next.js/releases/tag/v15.5.21Product, Release Notes
- https://github.com/vercel/next.js/releases/tag/v16.2.11Product, Release Notes
- https://github.com/vercel/next.js/security/advisories/GHSA-q8wf-6r8g-63chVendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.