Skip to main content
Vulnerability Database/CVE-2026-103004

CVE-2026-103004: Vercel Next.js Information Disclosure Flaw

CVE-2026-103004 is an information disclosure vulnerability in Vercel Next.js affecting versions 16.3.0 to 16.3.7. Cache handlers may leak data across different root params. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-103004 Overview

CVE-2026-103004 is a cache key confusion flaw in Vercel's Next.js framework affecting versions 16.3.0 through 16.3.7. The issue occurs when Cache Components are enabled (cacheComponents: true) and a use cache function invokes another use cache function that reads a root parameter through next/root-params. The enclosing function's cache key omits the root parameter, causing a single cached entry to serve responses across different root parameter values. The vulnerability is tracked under [CWE-524: Use of Cache Containing Sensitive Information]. Vercel patched the issue in Next.js 16.3.8.

Critical Impact

Content generated for one root parameter value can be served to requests for a different root parameter value, and shared cache headers can propagate the leaked content through downstream caches.

Affected Products

  • Vercel Next.js 16.3.0
  • Vercel Next.js versions 16.3.1 through 16.3.7
  • Node.js deployments with cacheComponents: true enabled

Discovery Timeline

  • 2026-10-01 - CVE-2026-103004 published to NVD
  • 2026-10-05 - Last updated in NVD database

Technical Details for CVE-2026-103004

Vulnerability Analysis

Next.js warms use cache handlers that depend on next/root-params during request processing. When Cache Components are active, an outer use cache function may call an inner use cache function that reads a root parameter. If the inner call is served from an existing cache entry, Next.js skips re-recording the root parameter dependency on the enclosing function. The outer entry is written once and keyed without that root parameter.

Subsequent requests for different root parameter values match the same cache key and receive the stored response. The leaked content is deterministic rather than attacker-controlled: whichever request writes the entry first determines what every other root parameter value receives. The flaw applies to prerendered pages, runtime-generated pages, and fully dynamic responses.

Root Cause

The root cause is incomplete dependency tracking during nested use cache warming. The cache key derivation for the enclosing function does not inherit root parameter reads performed by inner cached calls when those inner calls are served from a prior entry. This produces a key collision across tenants or locales represented by distinct root parameter values.

Attack Vector

An unauthenticated remote attacker does not need to craft malicious input. Normal traffic patterns across root parameter boundaries, such as multi-tenant routes keyed by [tenant] or localized paths keyed by [locale], trigger the condition. If responses carry shared cache headers, intermediate caches and content delivery networks redistribute the mismatched content to additional users, broadening exposure beyond the origin.

No exploit code is required. See the GitHub Security Advisory GHSA-h694-7cp9-m8p3 for the vendor's technical description.

Detection Methods for CVE-2026-103004

Indicators of Compromise

  • Responses served from Next.js caches that contain root parameter values inconsistent with the requested URL path segment.
  • Identical cached payloads returned for distinct [tenant], [locale], or other root-parameter route segments.
  • Cache-Control headers with public or s-maxage on routes that read root parameters inside nested use cache handlers.

Detection Strategies

  • Audit the Next.js project for cacheComponents: true in next.config.js combined with nested use cache functions that call next/root-params.
  • Compare rendered responses across all root parameter values during integration testing to detect cross-tenant content reuse.
  • Review build logs and runtime cache telemetry for entries whose keys do not include expected root parameters.

Monitoring Recommendations

  • Instrument downstream CDN and reverse proxy logs to flag cache HITs where the response body references a different tenant or locale than the request URL.
  • Alert on anomalous cross-tenant data appearances in error reporting or user-submitted bug reports after deploying Next.js 16.3.x releases.

How to Mitigate CVE-2026-103004

Immediate Actions Required

  • Upgrade Next.js to version 16.3.8 or later across all affected deployments.
  • Invalidate existing cache entries produced under vulnerable versions to prevent continued serving of mismatched content.
  • Purge downstream CDN and shared caches that may hold responses generated by Next.js 16.3.0 through 16.3.7.

Patch Information

Vercel addressed the vulnerability in Next.js 16.3.8. Release notes are available at Next.js Release v16.3.8. The vendor advisory is published as GHSA-h694-7cp9-m8p3.

Workarounds

  • Disable Cache Components by setting cacheComponents: false in next.config.js until the upgrade is deployed.
  • Refactor nested use cache handlers to avoid reading next/root-params from inner cached calls, or inline root parameter reads into the outermost cached function.
  • Set Cache-Control: private, no-store on routes that depend on root parameters to prevent downstream caches from amplifying mismatched responses.
bash
# Upgrade Next.js to the patched release
npm install next@16.3.8

# Verify the installed version
npx next --version

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.