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.
References
| Link | Resource |
|---|---|
| https://github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh | Vendor Advisory Mitigation |
Configurations
Configuration 1 (hide)
|
History
13 May 2026, 20:00
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* | |
| First Time |
Vercel next.js
Vercel |
|
| References | () https://github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh - Vendor Advisory, Mitigation |
13 May 2026, 17:25
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-05-13 17:16
Updated : 2026-05-13 20:00
NVD link : CVE-2026-44577
Mitre link : CVE-2026-44577
CVE.ORG link : CVE-2026-44577
JSON object : View
Products Affected
vercel
- next.js
CWE
CWE-770
Allocation of Resources Without Limits or Throttling