Next.js: Denial of Service in the Image Optimization API using SVGs (CVE-2026-64644) | HOL Guard CVE

Medium severityCVE-2026-64644GHSA-Q8WF-6R8G-63CH

Next.js: Denial of Service in the Image Optimization API using SVGs

Answer in brief

CVE-2026-64644 records a Medium severity vulnerability in Next.js: Denial of Service in the Image Optimization API using SVGs. The current sources do not mark it as known exploited. The current feed maps next (npm), next (npm), next (npm), next (npm). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jul 21, 2026Updated Jul 23, 2026Source checked Aug 24, 2026First seen by HOL Aug 8, 2026Material review Jul 23, 2026

Upstream Advisory

Key facts

Risk: Medium
Exploitation: Not marked as known exploited
Affected software: 4 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps next (npm), next (npm), next (npm), next (npm). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
nextnpm	>=15.5.0 <15.5.21	15.5.21
nextnpm	>=16.0.0 <16.2.11	16.2.11
nextnpm	>=15.5.0<15.5.21	Not reported
nextnpm	>=16.0.0<16.2.11	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for next, next, next.
Review the reported fix. Update next to 15.5.21; next to 16.2.11 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Jul 21, 2026
Evidence: source:ghsa:source_dates:source-dates:record
Source modified
Jul 23, 2026
Evidence: source:ghsa:source_dates:source-dates:record
First seen by HOL
Aug 8, 2026

Sources and claim methodology

Upstream source 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`.

Quoted source text, attributed separately from HOL analysis.