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`).
References
| Link | Resource |
|---|---|
| https://github.com/vercel/next.js/commit/39eb8e0ac498b48855a0430fbf4c22276a73b4bd | Patch |
| https://github.com/vercel/next.js/releases/tag/v16.1.7 | Release Notes |
| https://github.com/vercel/next.js/security/advisories/GHSA-3x4c-7xq6-9pq8 | Vendor Advisory Mitigation |
Configurations
History
No history.
Information
Published : 2026-03-18 01:16
Updated : 2026-03-18 19:52
NVD link : CVE-2026-27980
Mitre link : CVE-2026-27980
CVE.ORG link : CVE-2026-27980
JSON object : View
Products Affected
vercel
- next.js
CWE
CWE-400
Uncontrolled Resource Consumption
