Read the docs

Cache leak across root param values in Next.js nested use cache functions

Priority MEDIUM 43CWE-362Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Next.js from 16.2.0 before 16.4.5 is affected. When Cache Components are enabled, a nested 'use cache' call that reads a root param and returns pending promises can cause the outer cache entry to be stored under a key that omits the root param. A race between cache writes (CWE-362) lets the first written value be served for other root param values. An unauthenticated remote attacker can exploit this without attacker-controlled input, and the outer entry also ignores nested cache tag invalidation and lifetimes.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

Next.js is a React framework for building full-stack web applications. From 16.2.0 until 16.4.5, Next.js applications with Cache Components enabled can reuse an outer 'use cache' entry across root param values when a nested 'use cache' call reads a root param through next/root-params and returns a value containing pending promises. React Flight can deliver the ready portion to the outer function before the inner cache finishes publishing its root-param dependencies. The outer entry can then complete and be persisted under a key that omits the root param, causing the first written value to be served for other root param values and allowing the outer entry to ignore nested cache tag invalidation and lifetimes. The leaked value is not attacker controlled and depends on which invocation writes the entry first. This variant does not require an existing inner cache entry or a slow cache handler and is not covered by the fix for CVE-2026-103004. This issue is fixed in version 16.4.5.

Why it matters now

Fix Fixed next.js (vercel): 16.4.5

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
vercelnext.js16.2.0 to before 16.4.516.4.5Patch availableCNA
  • next.js Vendorvercel Affected 16.2.0 to before 16.4.5 Fixed in 16.4.5 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:vercel:next.js:*:*:*:*:*:*:*:*——vercel
  • cpe:2.3:a:vercel:next.js:*:*:*:*:*:*:*:* Versions — — ·vercel

Remediation

Upgrade Next.js to version 16.4.5, which fixes this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA next.js (vercel) Fixed in 16.4.5

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-119351

References

  • TI-2025-34861 Unsafe deserialization in React Server Components enables RCE KEVCVSS 3.1CRITICAL 10.0
  • TI-2025-21309 Authorization Bypass in Next.js Middleware CVSS 3.1CRITICAL 9.1
  • TI-2024-15745 An issue in Hyper on macOS version 3.4.1 and before, allows remote attackers to execute… CVSS 3.1CRITICAL 9.8
  • TI-2025-34863 Deserialization of untrusted data in Meta react-server-dom-webpack CVSS 3.1HIGH 7.5
  • TI-2024-31371 Cache Poisoning in next.js CVSS 3.1HIGH 7.5
  • TI-2023-24914 Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch… CVSS 3.1HIGH 7.5
See all 90 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences