MSRXMSRXSecurity
Vulnerabilities / CVE-2026-103004

CVE-2026-103004

Published 2026-10-01 · published (not yet in NVD)

CVE-2026-103004

next.js cache leak on warm `use cache` handlers accessing root param

6.3 MEDIUM
CVSS 4.0 · CNA
0.3%
chance of exploitation in the next 30 days (EPSS; higher than 16% of CVEs)

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.

Scores

Affected packages and fixed versions

PackageEcosystemFixed in
nextnpm16.3.8

Affected products

  • vercel next.js: < 16.3.8

Weakness: CWE-524

Also known as: GHSA-h694-7cp9-m8p3

2 references (advisories, patches, write-ups)

Sources: CVE.org, OSV.dev, FIRST EPSS. Missing ones did not answer or have no record yet.

Look up another CVECheck your dependenciesScan a website