要点
- CVE-2026-64644 是影响 next.js (vercel), next 的中危 (CVSS 5.3)漏洞。
- 未来 30 天内被利用的概率（EPSS）：0.67%，高于 51.9% 的漏洞。
- 修复：升级到 15.5.21, 16.2.11 或更高版本。
| Package | Affected versions | Patched versions |
|---|
| next.js | ≥ 15.5.0, < 15.5.21≥ 16.0.0, < 16.2.11
| 15.5.2116.2.11
|
| next npm | ≥ 15.5.0, < 15.5.21≥ 16.0.0, < 16.2.11
| 15.5.2116.2.11
|
Description
Impact
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.
- If you are using
config.images.remotePatterns, only the patterns in that array are impacted.
- If you are using
config.images.unoptimized: true, you are NOT impacted.
- If you are using
config.images.loader: 'custom', you are NOT impacted.
- If you are using Vercel, you are NOT impacted.
Workarounds
If you cannot upgrade immediately, you can avoid the expensive work by setting config.experimental.imgOptSkipMetadata : true.
NVD 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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free