Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration
Published 27 Jan 2026 · Updated 10 Sept 2026
Affected packages
- Affected
- >=10.0.0 <15.5.10
- Fixed in
- 15.5.10
npm install next@15.5.10- Affected
- >=15.6.0-canary.0 <16.1.5
- Fixed in
- 16.1.5
npm install next@16.1.5Details
A DoS vulnerability exists in self-hosted Next.js applications that have remotePatterns configured for the Image Optimizer. The image optimization endpoint (/_next/image) loads external images entirely into memory without enforcing a maximum size limit, allowing an attacker to cause out-of-memory conditions by requesting optimization of arbitrarily large images. This vulnerability requires that remotePatterns is configured to allow image optimization from external domains and that the attacker can serve or control a large image on an allowed domain.
Strongly consider upgrading to 15.5.10 and 16.1.5 to reduce risk and prevent availability issues in Next applications.
Is GHSA-9g9p-9gw9-jx7f in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected next, and gives you the command that fixes it.
References
- Linkgithub.com/vercel/next.js/security/advisories/GHSA-9g9p-9gw9-jx7f
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-59471
- Linkgithub.com/vercel/next.js/commit/500ec83743639addceaede95e95913398975156c
- Linkgithub.com/vercel/next.js/commit/e5b834d208fe0edf64aa26b5d76dcf6a176500ec
- Packagegithub.com/vercel/next.js
- Linkgithub.com/vercel/next.js/releases/tag/v15.5.10
- Linkgithub.com/vercel/next.js/releases/tag/v16.1.5
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.