How severe is GHSA-3x4c-7xq6-9pq8?

No CVSS score has been assigned to GHSA-3x4c-7xq6-9pq8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3x4c-7xq6-9pq8?

GHSA-3x4c-7xq6-9pq8 affects the following packages: next (npm), next (npm). Ecosystems affected: npm.

How do I fix GHSA-3x4c-7xq6-9pq8?

Update next to 16.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3x4c-7xq6-9pq8 is resolved across your whole dependency graph.

How do I detect GHSA-3x4c-7xq6-9pq8 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3x4c-7xq6-9pq8 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-3x4c-7xq6-9pq8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3x4c-7xq6-9pq8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-3x4c-7xq6-9pq8?

GHSA-3x4c-7xq6-9pq8 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 54th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3x4c-7xq6-9pq8?

GHSA-3x4c-7xq6-9pq8 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3x4c-7xq6-9pq8 published, and has it been updated?

GHSA-3x4c-7xq6-9pq8 was published on March 17, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Next.js: Unbounded next/image disk cache growth can exhaust storageGHSA-3x4c-7xq6-9pq8

Fix: vercel/next.js@39eb8e0

GHSA-3x4c-7xq6-9pq8 is a Uncontrolled Resource Consumption vulnerability in next. A fix is available for next — see the affected versions and patch details below.

Also known asCVE-2026-27980

Published

Mar 17, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-3x4c-7xq6-9pq8.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

61Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

nextnpm

92.1Mdownloads / week

Description

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)

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`next`	≥ 16.0.0-beta.0&&< 16.1.7	16.1.7`npm install next@16.1.7`
📦npm	`next`	≥ 10.0.0&&< 15.5.14	15.5.14`npm install next@15.5.14`

Affected Products

1 product · 1 configurations

Application

next.jsvercel

≥ 10.0.0 && < 16.1.7

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update next to 16.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3x4c-7xq6-9pq8 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability is rated as Moderate because, while an unauthenticated remote user can trigger unbounded cache allocation to exhaust filesystem storage and degrade service availability, it does not allow code execution or compromise data integrity and confidentiality. Within Red Hat environments utilizing Next.js…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-3x4c-7xq6-9pq8 (CC BY 4.0)

Product	Fixed in	Advisory
Streams for Apache Kafka 2.9.4	`com.github.streamshub-console`	RHSA-2026:34608
Streams for Apache Kafka 3.2.0	`com.github.streamshub-console`	RHSA-2026:13571

Frequently Asked Questions

## 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