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.
CVE-2026-64644
This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 50% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 50%
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 29, 2026
Advisory Details (5)
Auto-updated Jul 27, 2026Denial of Service in the Image Optimization API using SVGs · Advisory · vercel/next.js · GitHub
https://github.com/vercel/next.js/security/advisories/GHSA-q8wf-6r8g-63chv16.2.11
Patch available: vercel/next.js v16.2.11
https://github.com/vercel/next.js/releases/tag/v16.2.11v15.5.21
Patch available: vercel/next.js v15.5.21
https://github.com/vercel/next.js/releases/tag/v15.5.21fix(next/image): improve performance of detectContentType()
Patch available: vercel/next.js v16.3.0-canary.92 (PR #96006 merged 2026-07-21)
https://github.com/vercel/next.js/pull/96006commit 93cb90891402 (vercel/next.js)
Patch available: vercel/next.js v16.3.0-canary.92 (contains commit 93cb90891402)
https://github.com/vercel/next.js/commit/93cb90891402fa4c47798d03cb9e05c13233766cVendor Advisories for CVE-2026-64644(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | next | 2026-08-12 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| next | — | 16.2.11 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 62× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 111 total refreshes for this CVE.
- 2026-09-14 04:22 UTCEG score recompute
- 2026-09-14 04:22 UTCVendor advisory
- 2026-09-13 02:37 UTCEG score recompute
- 2026-09-13 02:37 UTCVendor advisory
- 2026-09-12 00:50 UTCEG score recompute
- 2026-09-12 00:50 UTCVendor advisory
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 21:14 UTCEG score recompute
- 2026-09-10 21:14 UTCVendor advisory
- 2026-09-09 09:11 UTCEG score recompute
- 2026-09-09 09:11 UTCVendor advisory
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 21:39 UTCEG score recompute
- 2026-09-07 21:39 UTCVendor advisory
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 19:33 UTCEG score recompute
- 2026-09-05 19:33 UTCVendor advisory
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-04 13:39 UTCEG score recompute
- 2026-09-04 13:39 UTCVendor advisory
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 23:30 UTCEG score recompute
Show 75 moreShow fewer
- 2026-09-01 23:30 UTCVendor advisory
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 02:36 UTCEG score recompute
- 2026-08-31 02:36 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-30 00:48 UTCEG score recompute
- 2026-08-30 00:48 UTCVendor advisory
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 14:46 UTCEG score recompute
- 2026-08-27 14:46 UTCVendor advisory
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 12:57 UTCEG score recompute
- 2026-08-26 12:57 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 11:12 UTCEG score recompute
- 2026-08-25 11:12 UTCVendor advisory
- 2026-08-24 09:26 UTCVendor advisory
- 2026-08-23 07:40 UTCEG score recompute
- 2026-08-23 07:40 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 05:55 UTCEG score recompute
- 2026-08-22 05:55 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 04:10 UTCEG score recompute
- 2026-08-21 04:10 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 02:24 UTCEG score recompute
- 2026-08-20 02:24 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 00:38 UTCEG score recompute
- 2026-08-19 00:38 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 22:39 UTCEG score recompute
- 2026-08-17 22:39 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 20:54 UTCEG score recompute
- 2026-08-16 20:54 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-15 19:09 UTCEG score recompute
- 2026-08-15 19:09 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 17:23 UTCEG score recompute
- 2026-08-14 17:23 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 15:30 UTCEG score recompute
- 2026-08-13 15:30 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 13:39 UTCEG score recompute
- 2026-08-11 11:53 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 10:08 UTCEG score recompute
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 08:23 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 06:38 UTCEG score recompute
- 2026-08-07 04:53 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 03:07 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 01:22 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 23:37 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 21:52 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 20:07 UTCEG score recompute
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:36 UTCEG score recompute
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-64644?
When was CVE-2026-64644 disclosed?
Is CVE-2026-64644 actively exploited?
What is the CVSS score of CVE-2026-64644?
How do I remediate CVE-2026-64644?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64644
Is Your Infrastructure Affected by CVE-2026-64644?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.