VulnerabilityAnalyzed

CVE-2026-27980

Starting in version 10.0.0 and prior to version 16.1.7, the default Next.js image optimization disk cache (`/_next/image`) did not have a configurable upper bound, allowing unbounded cache growth.

MEDIUM 6.9EPSS 0.68%

Does this matter?

Lower severity and a low EPSS score (0.68%). Track it; it rarely justifies an emergency change on its own.

Description

Next.js is a React framework for building full-stack web applications. Starting in version 10.0.0 and prior to version 16.1.7, the default Next.js image optimization disk cache (`/_next/image`) did not have a configurable upper bound, allowing unbounded cache growth. An attacker could generate many unique image-optimization variants and exhaust disk space, causing denial of service. This is fixed in version 16.1.7 by adding an LRU-backed disk cache with `images.maximumDiskCacheSize`, including eviction of least-recently-used entries when the limit is exceeded. Setting `maximumDiskCacheSize: 0` disables disk caching. If upgrading is not immediately possible, periodically clean `.next/cache/images` and/or reduce variant cardinality (e.g., tighten values for `images.localPatterns`, `images.remotePatterns`, and `images.qualities`).

CVSS 4.0: 6.9 MEDIUMCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M
EPSS: 0.68% probability · 51th percentile
CISA KEV: Not listed
Weakness: CWE-400
Affected: vercel/next.js
Source: security-advisories@github.com

References

https://github.com/vercel/next.js/commit/39eb8e0ac498b48855a0430fbf4c22276a73b4bdPatch
https://github.com/vercel/next.js/releases/tag/v16.1.7Release Notes
https://github.com/vercel/next.js/security/advisories/GHSA-3x4c-7xq6-9pq8Mitigation, Vendor Advisory

Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.