CVE-2026-94484: CWE-524: Use of Cache Containing Sensitive Information in vercel next.js
Next.js versions from 15.0.0 up to but not including 15.5.27, and from 16.0.0 up to but not including 16.3.8, contain a vulnerability where a shared response cache key is insufficiently scoped. This allows an unauthenticated attacker to poison the cache via a crafted request, potentially causing cross-user content substitution or persistent denial of service until the cache entry is refreshed. The issue is fixed in versions 15.5.27 and 16.3.8.
AI Analysis
Technical Summary
Next.js, a React framework for full-stack web applications, has a vulnerability (CVE-2026-94484) in versions >=15.0.0 <15.5.27 and >=16.0.0 <16.3.8 where applications with a root-level catch-all page and statically generated or Incremental Static Regeneration routes use a shared response cache key that is insufficiently scoped to the source route. This allows an unauthenticated attacker to poison the cache with a crafted request, leading to cross-user content substitution or persistent denial of service until the poisoned cache entry is revalidated or replaced. The vulnerability is addressed in versions 15.5.27 and 16.3.8.
Potential Impact
An unauthenticated attacker can poison the shared response cache, causing users to receive substituted content from other users or experience persistent denial of service until the cache entry is refreshed. This can affect application integrity and availability.
Mitigation Recommendations
Upgrade Next.js to version 15.5.27 or later in the 15.x series, or 16.3.8 or later in the 16.x series, where this vulnerability has been fixed. No other mitigation is indicated by the vendor advisory.
CVE-2026-94484: CWE-524: Use of Cache Containing Sensitive Information in vercel next.js
Description
Next.js versions from 15.0.0 up to but not including 15.5.27, and from 16.0.0 up to but not including 16.3.8, contain a vulnerability where a shared response cache key is insufficiently scoped. This allows an unauthenticated attacker to poison the cache via a crafted request, potentially causing cross-user content substitution or persistent denial of service until the cache entry is refreshed. The issue is fixed in versions 15.5.27 and 16.3.8.
CVSS v4.0
Score 6.3medium
Affected software
vercel
next.js
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Next.js, a React framework for full-stack web applications, has a vulnerability (CVE-2026-94484) in versions >=15.0.0 <15.5.27 and >=16.0.0 <16.3.8 where applications with a root-level catch-all page and statically generated or Incremental Static Regeneration routes use a shared response cache key that is insufficiently scoped to the source route. This allows an unauthenticated attacker to poison the cache with a crafted request, leading to cross-user content substitution or persistent denial of service until the poisoned cache entry is revalidated or replaced. The vulnerability is addressed in versions 15.5.27 and 16.3.8.
Potential Impact
An unauthenticated attacker can poison the shared response cache, causing users to receive substituted content from other users or experience persistent denial of service until the cache entry is refreshed. This can affect application integrity and availability.
Mitigation Recommendations
Upgrade Next.js to version 15.5.27 or later in the 15.x series, or 16.3.8 or later in the 16.x series, where this vulnerability has been fixed. No other mitigation is indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-09-21T17:25:42.292Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6abfce5fa43b0b3b89cf6dfa
Added to database: 10/02/2026, 15:31:43 UTC
Last enriched: 10/02/2026, 15:46:25 UTC
Last updated: 10/02/2026, 15:46:25 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.