Bug 2448509 (CVE-2026-27980) - CVE-2026-27980 next.js: Next.js: Unbounded next/image disk cache growth can exhaust storage
Summary: CVE-2026-27980 next.js: Next.js: Unbounded next/image disk cache growth can e...
Keywords:
Status: NEW
Alias: CVE-2026-27980
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2448729 2448731 2448732 2448738
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-03-18 01:02 UTC by OSIDB Bzimport
Modified: 2026-03-18 18:45 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-03-18 01:02:00 UTC
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`).


Note You need to log in before you can comment on or make changes to this bug.