CVE-2026-103004 · GHSA-h694-7cp9-m8p3
next.js cache leak across root param values in nested 'use cache' functions
- Risk score
- 40/100
- CVSS
- 5.3 v3.1
- Exploit chance (30 days)
- 0.2%
- Published
- 1 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 incorrect…
- Affected
- next (npm) >= 16.3.0, < 16.3.8
- Fix
- Upgrade next to 16.3.8 or later.
- Exploitation
- No known exploitation
Story map
At a glance
next: Yellow, plan it in. Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, Image Optimization can follow attacker-controlled DNS resolution for a remote URL that matches images.remotePatterns, allowing the optimized image fetch to reach private IP addresses after the URL passes the allow-list che…
The flaws
- CVE-2026-103004: Next.js cache leak across root param values in nested 'use cache' functions (CVSS 5.3 · EPSS 0%)
- CVE-2026-94483: Next.js has Server-Side Request Forgery in Image Optimization (CVSS 6.5 · EPSS 0%)
- CVE-2026-94543: Next.js has cache poisoning of SSG and ISR pages in self-hosted applications (CVSS 5.3 · EPSS 1%)
The fix
Upgrade next: 16.3.8 · 15.5.27 or later on your release line
Who is exposed: next (npm) >= 16.0.0, < 16.3.8
Where it stands
- No known exploitation
Connects to
- Same weakness: CWE-524 (CWE-524). 3 other warnings in 30 days
- Same product: Earlier next warnings. 4 in the last 90 days
Why it is Yellow
- CVSS 5.3 medium
- On your watchlist: npm
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| next | npm | >= 16.3.0, < 16.3.8 | 16.3.8 |
References
- https://github.com/advisories/GHSA-h694-7cp9-m8p3
- https://github.com/vercel/next.js/security/advisories/GHSA-h694-7cp9-m8p3
- https://nvd.nist.gov/vuln/detail/CVE-2026-103004
- https://github.com/vercel/next.js/commit/e92db4536a7f34ae2dbda583cfa1b4e0d06d1865
- https://github.com/vercel/next.js/releases/tag/v16.3.8
- https://github.com/advisories/GHSA-h694-7cp9-m8p3
Original description
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.
Last activity 1 Oct 2026. Patch Forecast updates every hour.