| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-q8wf-6r8g-63ch | Next.js: Denial of Service in the Image Optimization API using SVGs |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 29 Jul 2026 08:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 29 Jul 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Tue, 28 Jul 2026 03:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Vercel
Vercel next.js |
|
| Vendors & Products |
Vercel
Vercel next.js |
Mon, 27 Jul 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Next.js: Denial of Service in the Image Optimization API using SVGs | |
| Weaknesses | CWE-407 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-07-27T18:35:41.443Z
Reserved: 2026-07-20T17:11:30.895Z
Link: CVE-2026-64644
Updated: 2026-07-27T18:35:38.079Z
No data.
OpenCVE Enrichment
Updated: 2026-07-28T15:00:04Z
Github GHSA