vercel · Next.js · published 2026-05-13

CVE-2026-44577Next.js: Denial of Service in the Image Optimization API

Routine No exploitation evidence; EPSS 0.7%.

CVE-2026-44577 is not known to be exploited in the wild. EPSS estimates a 0.7% chance of exploitation in the next 30 days, higher than 55% of all CVEs. This Next.js vulnerability: CVSS 5.9 (v3.1). Fixed upstream in Next.js 16.2.5, 15.5.16. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Next.js 16.2.5, 15.5.16.

Patch events

  1. This monthSecurity release

    Web frameworkNext.js

    Next.js security releases: 16.2.5, 15.5.16

    Upgrade to 16.2.515.5.16

    Why: CVE-2026-44578: EPSS 36% with high severity (CVSS 8.6).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.7% (55th pct)FIRST EPSS v2026.06.15
CVSS base score5.9 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →