# CVE-2025-59471: Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration > Attackers can cause out-of-memory denial of service in Next.js apps by requesting optimization of large external images when remotePatterns are configured. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Jan 2026 - **Updated:** 27 Jan 2026 - **Also known as:** CLEANSTART-2026-TD56649, CLSA-2026-1792195749, CLSA-2026-1792196878, CLSA-2026-1792206305, CLSA-2026-1792272231, CLSA-2026-1792293017, CLSA-2026-1792304742, CLSA-2026-1792326305, CLSA-2026-1792338238, CLSA-2026-1792358589, CLSA-2026-1792364006, GHSA-9g9p-9gw9-jx7f, MINI-cgrv-pfmx-27vx, ROOT-APP-NPM-CVE-2025-59471 ## What is CVE-2025-59471? CVE-2025-59471 is a medium-severity denial of service vulnerability in Vercel Next.js, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A denial of service 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 or 16.1.5 to reduce risk and prevent availability issues in Next applications. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2025-59471? 4 open source packages ship an affected version, including next. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `next` | npm | From 10.0.0 | 15.5.10 | | `next` | npm | From 10.0.0 | 15.5.10 | | `next` | npm | From 15.6.0-canary.0 | 16.1.5 | | `next` | npm | From 15.6.0-canary.0 | 16.1.5 | Products: Vercel Next.js. ## How do I fix CVE-2025-59471? Upgrade next to a fixed version for your release line: 15.5.10 or 16.1.5. ## Is CVE-2025-59471 being exploited? There is no known exploitation of CVE-2025-59471 in the wild and no public exploit code. ## Other vulnerabilities in Vercel Next.js - [CVE-2025-29927](https://insights.sbomify.com/CVE-2025-29927/): Authorization Bypass in Next.js Middleware (critical 9.1) - [CVE-2026-44578](https://insights.sbomify.com/CVE-2026-44578/): Next.js: Server-side request forgery in applications using WebSocket upgrades (high 8.6) - [CVE-2026-94483](https://insights.sbomify.com/CVE-2026-94483/): Next.js: Server-Side Request Forgery in Image Optimization (high 8.3) - [CVE-2026-64642](https://insights.sbomify.com/CVE-2026-64642/): Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale (high 8.3) - [CVE-2026-64645](https://insights.sbomify.com/CVE-2026-64645/): Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname (high 8.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-59471 and fix it if it is affected. What it is: CVE-2025-59471 is a medium-severity denial of service vulnerability in Vercel Next.js, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-59471 in the wild and no public exploit code. Affected packages and fixed versions: - next (npm): affected from 10.0.0; fixed in 15.5.10 - next (npm): affected from 10.0.0; fixed in 15.5.10 - next (npm): affected from 15.6.0-canary.0; fixed in 16.1.5 - next (npm): affected from 15.6.0-canary.0; fixed in 16.1.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-59471/ (Markdown: https://insights.sbomify.com/CVE-2025-59471/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59471 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59471 - OSV: https://osv.dev/vulnerability/CVE-2025-59471 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-59471/ Summaries are generated and may contain mistakes; the official description above is the record.