CVE-2026-44577: Next.js: Denial of Service in the Image Optimization API
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.
Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker may exhaust a self-hosted Next.js server’s memory by making its image service load a permitted, unusually large local image. Successful abuse can crash or disrupt the application. Hosted configurations not using the default Next.js image loader are not established as affected by the supplied evidence.
Executive priority
Prioritize remediation for public, self-hosted Next.js services because unauthenticated requests could cause outages. Upgrade promptly, especially where the image endpoint is internet-accessible or local patterns are unrestricted. Treat internal or non-default-loader deployments as verification priorities rather than automatically affected systems.
Technical view
Next.js 10.0.0 through 15.5.15 and 16.0.0 through 16.2.4 can read local assets entirely into memory through /_next/image without a size limit. The asset must match images.localPatterns, whose default allows all patterns. This is CWE-770 with CVSS 3.1 score 7.5, affecting availability only. Fixes are 15.5.16 and 16.2.5.
Likely exposure
Exposure requires self-hosted Next.js, an affected version, the default image loader, and reachable /_next/image requests for qualifying local assets. Risk is greater where large local files exist and images.localPatterns remains broadly permissive. The bundle does not establish exposure for managed hosting, custom loaders, or deployments without this endpoint.
Exploitation context
The attack has network reachability, low complexity, and needs neither authentication nor user interaction. However, CVE-2026-44577 is not listed as KEV in the supplied bundle, and the cited information provides no evidence of active exploitation. Absence from KEV does not prove exploitation is not occurring.
Researcher notes
The failure is unbounded memory consumption while processing qualifying local images, not a confidentiality or integrity issue. Assessment should correlate runtime version, hosting model, loader configuration, localPatterns, available asset sizes, endpoint reachability, and memory limits. Avoid destructive proof-of-concept testing in production; configuration inspection and controlled staging validation are safer.
Mitigation direction
Upgrade affected 15.x deployments to Next.js 15.5.16 or later.
Upgrade affected 16.x deployments to Next.js 16.2.5 or later.
Restrict images.localPatterns to required local assets as temporary exposure reduction.
Consult the Next.js advisory if upgrading immediately is not possible.
Validation and detection
Confirm the deployed Next.js version from build artifacts or dependency lockfiles.
Verify whether production is self-hosted and uses the default image loader.
Inspect images.localPatterns for broad or default access to local assets.
Confirm whether /_next/image is externally reachable without authentication.
Review memory-pressure, restart, and availability telemetry for unusual image requests.
Validate the upgrade in staging without deliberately loading oversized assets.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.