Description
Next.js is a React framework for building full-stack web applications. From 10.0.0 to before 15.5.16 and 16.2.5, when self-hosting Next.js with the default image loader, the Image Optimization API fetches local images entirely into memory without enforcing a maximum size limit. An attacker could cause out-of-memory conditions by requesting large local assets from the /_next/image endpoint that match the images.localPatterns configuration (by default, all patterns are allowed). This vulnerability is fixed in 15.5.16 and 16.2.5.
Affected products
vercel: next.js
References8
- github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jq… MitigationVendor Advisory
- access.redhat.com/errata/RHSA-2026:34608
- access.redhat.com/errata/RHSA-2026:37272
- access.redhat.com/errata/RHSA-2026:40974
- access.redhat.com/errata/RHSA-2026:54435
- access.redhat.com/security/cve/CVE-2026-44577
- bugzilla.redhat.com/show_bug.cgi?id=2477194
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44577…
Metrics
- CVSS 3.1
-
5.9
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 1% percentile: 55 · as of 14 November 2026
- CWE
- CWE-770
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.