cve.bz

CVE-2026-103004 vercel next.js

6.3 mediumEPSS 0.2%Fix available

Medium (6.3) in vercel next.js. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in next 16.3.8.

On this page
Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return value to pages with different root params. With Cache Components enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function's cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further. What values are leaked cannot be attacker controlled. Which value's content is served depends only on which invocation wrote the entry first. This has been patched in 16.3.8.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-524 Use of Cache Containing Sensitive Information
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-103004 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103004?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103004?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-103004 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
vercel:next.jsfrom 16.3.0 before 16.3.8

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-h694-7cp9-m8p3npmnext>=16.3.0 <16.3.816.3.8

Red Hat

Red Hat rates this Low.

Red Hat's statement

This low impact information disclosure flaw affects the Next.js framework (npm package `next`), which is present as a dependency in Red Hat Enterprise Linux 7, 8, 9, and 10 (via the firefox and thunderbird components) and in Red Hat In-Vehicle OS. When the non-default Cache Components feature is enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing cache entry: the enclosing function's cache key then omits that root param. The cache entry is written once and reused for all root param values, so an unauthenticated remote user can receive cached application responses that were produced for a different root param value — whether the page is prerendered at build time or at runtime, or rendered dynamically — and shared cache headers allow downstream caches to redistribute the exposed content further. What values are leaked cannot be controlled by an attacker, and which value's content is served depends only on which invocation wrote the cache entry first. Red Hat's low severity rating (CVSS 3.7) differs from the upstream moderate rating (NIST 5.3, CVEORG 6.3) because exploitation requires the non-default cacheComponents configuration and a specific nested 'use cache' architecture, depends on invocation timing beyond the attacker's control, and results only in limited confidentiality impact. Because the impact is low, the fix for the affected Red Hat products is deferred, leaving a residual risk of limited cross-context exposure of cached content in applications that use the affected configuration.

Red Hat's mitigation

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. The upstream project reports that there are no known workarounds and that applications should upgrade to the patched version, which is available as of Next.js 16.3.8.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10firefoxFix deferred
Red Hat Enterprise Linux 10thunderbirdFix deferred
Red Hat Enterprise Linux 7firefoxFix deferred
Red Hat Enterprise Linux 8firefoxFix deferred
Red Hat Enterprise Linux 8thunderbirdFix deferred
Red Hat Enterprise Linux 9firefoxFix deferred
Red Hat Enterprise Linux 9thunderbirdFix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gaudi-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-rocm-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/disk-image-cuda-rhel9Fix deferred
Red Hat Trusted Artifact Signerrhtas/rekor-search-ui-rhel9Out of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-103004.

Attack patterns (CAPEC)

  • CAPEC-204 Lifting Sensitive Data Embedded in Cache Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON