Read the docs

Cross-user cache sharing in Next.js use cache with binary arguments

Priority LOW 25CWE-694Published · Updated

Key facts

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

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

Summary

Vercel Next.js from 16.0.0 before 16.4.5 is affected. App Router applications that pass binary arguments, such as Uint8Array or Blob values, to functions marked with the 'use cache' directive can generate identical cache keys for distinct arguments (CWE-694). A remote unauthenticated attacker can get requests with different binary arguments to share a cached result, disclosing cached data to other users or poisoning results returned to them.

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.0.0 until 16.4.5, Next.js App Router applications that pass binary arguments, such as Uint8Array or Blob values, to functions using the 'use cache' directive can generate identical cache keys for distinct arguments. Requests with different binary arguments can therefore share a cached result, causing cross-user disclosure of cached data or allowing one request to poison results returned to another user. This issue is fixed in version 16.4.5.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
Fix Fixed next.js (vercel): 16.4.5

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
vercelnext.js16.0.0 to before 16.4.516.4.5Patch availableCNA
  • next.js Vendorvercel Affected 16.0.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 Vercel Next.js to version 16.4.5.

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-119349
  2. 2026-11-16 CISA SSVC decision points changed

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