PT-2026-39410 · Vercel · Next.Js
CVE-2026-44577
·
Published
2026-05-06
·
Updated
2026-08-17
CVSS v2.0
7.8
High
| Vector | AV:N/AC:L/Au:N/C:N/I:N/A:C |
Name of the Vulnerable Software and Affected Versions
Next.js versions 10.0.0 through 15.5.15
Next.js versions 16.0.0 through 16.2.4
Description
When self-hosting with the default image loader, the Image Optimization API fetches local images entirely into memory without enforcing a maximum size limit. An attacker can trigger out-of-memory conditions by requesting large local assets from the '/ next/image' endpoint that match the
images.localPatterns configuration, which allows all patterns by default.Recommendations
Update to version 15.5.16.
Update to version 16.2.5.
As a temporary workaround, avoid routing large local assets through '/ next/image', disable image optimization for large or untrusted local files, or block image optimization access to those assets at the edge.
Disable the affected functionality using the
images.localPatterns: [] configuration.
Adjust the images.maximumResponseBody configuration to apply response size limits.Exploit
Fix
DoS
Allocation of Resources Without Limits
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Next.Js