Skip to content
OpenAdvisories
Medium · 6.9 CVE-2026-27980 EUVD-2026-12694GHSA-3x4c-7xq6-9pq8

Next.js: Unbounded next/image disk cache growth can exhaust storage

Published Mar 18, 2026 · Updated Mar 18, 2026 · Assigned by GitHub_M

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`).

Affected products

VendorProductAffectedFixed
vercel next.js >= 10.0.0, < 16.1.7 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling jitsucom-jitsu-console 2.11.0-r17 —
Wolfi rolling langfuse-3 3.162.0-r0 —

Affected packages

EcosystemPackageAffectedFixedRecord
npm next >= 16.0.0-beta.0, < 16.1.7 16.1.7 GHSA-3x4c-7xq6-9pq8
npm next >= 10.0.0, < 15.5.14 15.5.14 GHSA-3x4c-7xq6-9pq8

Advisories 1

References