No access to your tenant or devices. Every item links to its source. What this means
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`).
Read the publisher's advisoryNext.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`).
Read the publisher's advisoryNext.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`).
Read the publisher's advisory## Summary The default Next.js image optimization disk cache (`/_next/image`) did not have a configurable upper bound, allowing unbounded cache growth. ## Impact An attacker could generate many unique image-optimization variants and exhaust disk space, causing denial of service. Note that this does not impact platforms that have their own image optimization capabilities, such as Vercel. ## Patches Fixed 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. ## Workarounds If upgrade is not immediately possible: - Periodically clean `.next/cache/images`. - Reduce variant cardinality (e.g., tighten values for `images.localPatterns`, `images.remotePatterns`, and `images.qualities`)
Read the publisher's advisoryVendor product
Shown as published. These rules are not interpreted as NuGet package version ranges.
{
"vendor": "vercel",
"product": "next.js",
"versions": [
{
"version": ">= 10.0.0, < 16.1.7",
"status": "affected"
}
]
}Original source record · Cite this exact observation · Complete original publisher JSON
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
datePublished: Mar 18, 2026, 12:23:34 AM
dateUpdated: Mar 18, 2026, 7:50:12 PM
RHSA-2026:13571: Red Hat Security Advisory: Streams for Apache Kafka 3.2.0 release and security update
CVE-2024-29371 · CVE-2024-34351 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-62718 · CVE-2025-68121 · CVE-2026-1002 · CVE-2026-4800 · CVE-2026-23864 · CVE-2026-27980 · CVE-2026-33870 · CVE-2026-33871 · CVE-2026-40175
RHSA-2026:34608: Red Hat Security Advisory: Streams for Apache Kafka 2.9.4 release and security update
CVE-2024-29371 · CVE-2025-13465 · CVE-2025-58056 · CVE-2026-1002 · CVE-2026-4800 · CVE-2026-6860 · CVE-2026-23864 · CVE-2026-24281 · CVE-2026-24308 · CVE-2026-27980 · CVE-2026-33870 · CVE-2026-33871 · CVE-2026-34480 · CVE-2026-39852 · CVE-2026-41240 · CVE-2026-42044 · CVE-2026-42583 · CVE-2026-42587 · CVE-2026-44249 · CVE-2026-44573 · CVE-2026-44574 · CVE-2026-44575 · CVE-2026-44577 · CVE-2026-44578 · CVE-2026-44579 · CVE-2026-44893 · CVE-2026-45109 · CVE-2026-45416 · CVE-2026-45674 · CVE-2026-47691 · CVE-2026-48043 · CVE-2026-48059 · CVE-2026-50010 · CVE-2026-50559
WID-SEC-W-2026-0748: Vercel Next.js: Mehrere Schwachstellen
CVE-2026-27979 · CVE-2026-27980 · CVE-2026-29057 · CVE-2026-27977 · CVE-2026-27978
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-400
published: 2026-03-18T01:16:04.957
lastModified: 2026-06-17T10:28:00.700
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON
npm
SEMVER · introduced 16.0.0-beta.0 → fixed 16.1.7
npm
SEMVER · introduced 10.0.0 → fixed 15.5.14
Original source record · Cite this exact observation · Complete original publisher JSON