dbcve.org
Next.jsApplication · Vercel

CVE-2025-59471

HIGH · 7.5 CVSS v3.1 Published 2026-01-26
Fix available
A fix is available. Upgrade to 15.5.10 / 16.1.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A denial of service vulnerability in self-hosted Next.js Image Optimizer allows attackers to cause out-of-memory conditions by requesting optimization of arbitrarily large images. The `/_next/image` endpoint loads external images entirely into memory without enforcing a maximum size limit when `remotePatterns` is configured.

MitigationUpgrade to Next.js 15.5.10 or 16.1.5 and audit `remotePatterns` configuration to restrict allowed domains to only trusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Next.jsApplication
Affected:>= 10.0.0, < 15.5.10>= 16.0.0, < 16.1.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Next.js deployment type
    Determine if your Next.js application is self-hosted (running on your own infrastructure/server) rather than deployed on Vercel's platform. Check if you have a next.config.js or next.config.mjs file and control the server environment.
    Affected if The application is self-hosted with a custom server configuration.
  2. Check the installed Next.js version
    Run `npm list next` or `cat package.json` to find the installed Next.js version number.
    Affected if The version is >= 10.0.0 and < 15.5.10, or >= 16.0.0 and < 16.1.5.
  3. Verify remotePatterns is configured
    Examine your next.config.js, next.config.mjs, or next.config.ts file and search for the `remotePatterns` configuration option under the `images` object.
    Affected if remotePatterns is defined and allows external image domains.
  4. Confirm image optimization endpoint is accessible
    Check if the `/_next/image` endpoint is accessible on your self-hosted server. This endpoint is used for on-demand image optimization.
    Affected if The endpoint is publicly accessible without additional authentication on a self-hosted deployment.

You are affected if you are running a self-hosted Next.js instance with a version in the affected ranges and have remotePatterns configured, allowing the image optimizer to load external images into memory without size limits.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 15.5.10 / 16.1.5 or later
Fixed in 15.5.1016.1.5
Interim mitigation

Upgrade to Next.js 15.5.10 or 16.1.5 and audit `remotePatterns` configuration to restrict allowed domains to only trusted sources.

Recommended fix High confidence

15.5.10 (for Next.js 15.x) or 16.1.5 (for Next.js 16.x)

  1. Identify your current Next.js version by checking package.json
  2. Run `npm list next` or `yarn list next` to confirm the installed version
  3. If on Next.js 15.x: upgrade to 15.5.10 by running `npm install [email protected]` or `yarn add [email protected]`
  4. If on Next.js 16.x: upgrade to 16.1.5 by running `npm install [email protected]` or `yarn add [email protected]`
  5. After upgrading, verify the installation with `npm list next`
  6. Restart your development server or production deployment to load the patched version
  7. Test image optimization functionality with `/_next/image` endpoint to ensure it works correctly
Caveat Minor/patch upgrades typically have low risk; review Next.js release notes for any deprecation notices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Next.js Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59471 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59471 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data