Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-119351

Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata

Overview

Published
16 Nov 2026
Modified
16 Nov 2026
Medium CVE
1 Registry packages
0 OS packages
0 Linux distributions
Yes Fix available
CVSS score Medium, no score

Description

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.

Source: OX vulnerability database

Severity

MEDIUM

No CVSS vector in the source. Severity comes from the advisory.

Weakness: CWE-362

Affected packages · 1

Packages affected by CVE-2026-119351
EcosystemPackageVulnerableFixed in
npm next >=16.2.0, <16.4.5 16.4.5

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.