Read the docs

Race condition in Next.js leaks cached data across root params

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 and GitHub.

Summary

Next.js from 16.3.0 before 16.4.5 can disclose cached data across root params when a 'use cache' function is called both directly during rendering and through unstable_cache(). A race in cross-request deduplication during the first fill after a cold process start lets a concurrent unstable_cache() request receive a result that is then cached under a key omitting root params, so later requests for other root param values can get the same entry (CWE-362). An unauthenticated remote attacker can exploit this only by sending an unstable_cache() request while the first fill is in flight.

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.3.0 until 16.4.5, Next.js applications using the same 'use cache' function directly during rendering and through unstable_cache() can disclose cached data across root params when that function reads a root param. During the first fill after a cold process start, cross-request deduplication allows a concurrent unstable_cache() request to join the direct call's in-flight fill and receive its result before the root param mismatch is rejected. unstable_cache() then persists that result under a key that omits root params, causing later requests for other root param values to receive the same entry until revalidation or eviction. Exploitation requires the unstable_cache() request to arrive while the first fill is in flight. Outside this race, nesting 'use cache' inside unstable_cache() raises an unsupported-operation error, and avoiding that nesting prevents the issue. This issue is fixed in version 16.4.5.

Why it matters now

Fix Fixed next.js (vercel): 16.4.5next (npm): 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.3.0 to before 16.4.516.4.5Patch availableCNA
—next (npm)16.3.0 to before 16.4.516.4.5Patch availableGHSA-mfr8-8qww-v76h
  • next.js Vendorvercel Affected 16.3.0 to before 16.4.5 Fixed in 16.4.5 Patch available CNA
  • next (npm) Vendor— Affected 16.3.0 to before 16.4.5 Fixed in 16.4.5 Patch available GHSA-mfr8-8qww-v76h

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 (npm package next) to version 16.4.5. Until the upgrade, avoid nesting 'use cache' functions inside unstable_cache(), which avoids the issue.

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

  • Fix · CNA next.js (vercel) Fixed in 16.4.5
  • Fix · GHSA-mfr8-8qww-v76h next (npm) Fixed in 16.4.5 Advisory →

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-119790
  2. 2026-11-16 Alias added: GHSA-mfr8-8qww-v76h
  3. 2026-11-16 Fix available: npm/[email protected] · GHSA-mfr8-8qww-v76h
  4. 2026-11-16 CVSS score added · GHSA-mfr8-8qww-v76h
  5. 2026-11-16 Weakness changed · GHSA-mfr8-8qww-v76h
  6. 2026-11-16 5 new references · GHSA-mfr8-8qww-v76h

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