vercel · Next.js · published 2026-03-18
CVE-2026-27980Next.js: Unbounded next/image disk cache growth can exhaust storage
Routine No exploitation evidence; EPSS 0.8%.
CVE-2026-27980 is not known to be exploited in the wild. EPSS estimates a 0.8% chance of exploitation in the next 30 days, higher than 56% of all CVEs. This Next.js vulnerability: CVSS 6.9 (v4.0), attacks can be automated. Fixed upstream in Next.js 16.1.7, 15.5.14, 15.5.13. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Next.js 16.1.7, 15.5.14, 15.5.13.
Patch events
Web frameworkNext.js
Next.js security releases: 16.1.7, 15.5.14, 15.5.13
Upgrade to
16.1.715.5.1415.5.13Why: Vendor security release for server software (most severe: CVE-2026-27979).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.8% (57th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.9 (v4.0)CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- vercel next.js
>= 10.0.0, < 16.1.7(affected)
Description (from the CVE record)#
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`).
Quoted from the CVE Program record.