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
This issue can let an unauthenticated internet user exhaust memory on affected self-hosted Next.js applications. The impact is availability: the site or service may slow down or crash. Sources identify fixed Next.js versions, but do not state active exploitation.
Executive priority
Prioritize remediation for public self-hosted Next.js services because exploitation could cause outages without authentication. Treat this as an availability risk, not a confirmed breach indicator.
Technical view
Affected self-hosted Next.js versions fetch eligible local images through the default Image Optimization API without a maximum size limit. Requests to /_next/image for large local assets matching images.localPatterns can trigger out-of-memory conditions. The CVSS 3.1 score is 7.5, with network attack vector and high availability impact.
Likely exposure
Exposure is most likely in self-hosted Next.js applications running versions >=10.0.0 and <15.5.16, or >=16.0.0 and <16.2.5, using the default image loader and reachable Image Optimization API.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. The issue is remotely reachable, requires no authentication or user interaction, and targets service availability rather than data confidentiality or integrity.
Researcher notes
Evidence is strong for affected versions, root cause, endpoint, and fixed releases. Evidence is incomplete for exploitation in the wild and for formal mitigations beyond upgrading. Avoid assuming Vercel-hosted exposure unless vendor guidance says so.
Mitigation direction
Upgrade affected Next.js 15.x deployments to 15.5.16 or later.
Upgrade affected Next.js 16.x deployments to 16.2.5 or later.
Inventory self-hosted Next.js applications using the default image loader.
Review Vercel and Red Hat advisories for package-specific guidance.
Check vendor guidance before applying temporary configuration workarounds.
Validation and detection
Confirm each application’s installed Next.js version.
Confirm whether the deployment is self-hosted.
Review Next.js image loader configuration for default loader usage.
Check whether /_next/image is internet reachable.
Verify remediation by confirming patched versions in build artifacts.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.