CVE-2026-103004 json
next.js cache leak on warm `use cache` handlers accessing root param
published 2026-09-30 39 d ago modified 2026-10-22 17 d ago also EUVD-2026-90872 , GHSA-h694-7cp9-m8p3
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm next 16.3.8
- vercel next.js 16.3.8
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-103004 updated cvss 3.7
next: Next.js: Information disclosure via cache key omission in nested cache handlers
-
Red Hat Enterprise Linux 7 firefox, firefox 140.14.0-1.el10_0 Red Hat Enterprise Linux 8 firefox, thunderbird, firefox 140.14.0-1.el10_0, thunderbird 140.14.0-1.el10_0 Red Hat Enterprise Linux 9 firefox, firefox-x11, thunderbird, firefox 140.14.0-1.el10_0, thunderbird 140.14.0-1.el10_0 Red Hat Enterprise Linux 10 firefox 140.14.0-1.el10_0, thunderbird 140.14.0-1.el10_0 Red Hat Enterprise Linux AI (RHEL AI) 3 rhelai3/bootc-cuda-rhel9, rhelai3/bootc-rocm-rhel9, rhelai3/bootc-gaudi-rhel9, rhelai3/disk-image-cuda-rhel9affected: workaround, no fix available “Fix deferred”
-
Red Hat Trusted Artifact Signer rhtas/rekor-search-ui-rhel9affected: workaround, no fix planned “Out of support scope”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 38 d ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.3 | 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 |
| CNA | 4.0 | 6.3 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | next | >=16.3.0, <16.3.8 |
16.3.8 |
Affected products
- vercel next.js
Classification
- Weakness
-
- CWE-524 Use of Cache Containing Sensitive Information
- Technology feeds
References
-
github.com
/vercel/next.js/commit/e92db4536a7f34ae2dbda583cfa1b4e0d06d1865
web
-
github.com
/vercel/next.js/security/advisories/GHSA-h694-7cp9-m8p3
web, vendor-advisory, advisory
-
github.com
/vercel/next.js/releases/tag/v16.3.8
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-103004
advisory
-
github.com
/vercel/next.js
package
Sources
- CVE List CVE-2026-103004
- GitHub Advisory GHSA-h694-7cp9-m8p3
- NVD CVE-2026-103004
- Maintainer advisory GHSA-h694-7cp9-m8p3
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of vercel/next.js published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.