CVE-2026-103004(vercel / next.js)

LOWCVSS 5.3 · MEDIUM

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-524

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • next.js

Affected systems

Vendors
Products
next.js

Deep dive

Full discourse1 post
  • DailyCVE@dailycve

    🟠 Nextjs, Cache leak across root param values in nested 'use cache' functions, #CVE-2026-103004 (Moderate severity) -DC-Oct2026-3618 https://dailycve.com/nextjs-cache-leak-across-root-param-values-in-nested-use-cache-functions-cve-2026-103004-moderate-severity-dc-oct2026-3618/

    0000051
    243 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appvercelnext.js-node.js-

Explore more