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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.9 · vercelNVD modified 2026-10-26 17:10
Affected (CPE criteria) 1
cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
References 8
- https://github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh Mitigation, Vendor Advisory
- https://access.redhat.com/errata/RHSA-2026:34608
- https://access.redhat.com/errata/RHSA-2026:37272
- https://access.redhat.com/errata/RHSA-2026:40974
- https://access.redhat.com/errata/RHSA-2026:54435
- https://access.redhat.com/security/cve/CVE-2026-44577
- https://bugzilla.redhat.com/show_bug.cgi?id=2477194
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44577.json