Packages / next / Security

ModerateVulnerabilityGHSA-vc7v-qv4w-wrv8CVE-2026-119351Published 17 Nov 2026

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

Your version

Affected releases · next

  • 16.x16.2.0 – 16.4.4Fixed in 16.4.5

On 16.x, the newest line:

npm install next@16.4.5
Every release on a timeline
  1. Not affected

    0.1.0 – 16.1.7

    399 releases

  2. Affected

    16.2.0 – 16.4.4

    27 releases

  3. Fixed

    16.4.5 – 16.4.6

    2 releases

428 stable releases of next, oldest to newest.

What happens

With Cache Components enabled, an outer 'use cache' function can be keyed incorrectly even when its inner 'use cache' call generates a fresh entry. If the inner function reads a root param (via next/root-params) and returns a value that still contains pending promises — for example an object with data that is ready immediately alongside slower data — React Flight delivers the ready portion to the outer function before the inner entry has finished publishing its root param dependencies. The outer function can then finish, and its cache entry is persisted under a key that omits that root param. The 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. Entries written this way can also ignore tag invalidation and cache lifetimes of the nested caches they consumed.

What values are leaked cannot be attacker controlled. Which value's content is served depends only on which invocation wrote the entry first.

This is a variant of github.com/advisories/GHSA-h694-7cp9-m8p3 that the fix for that advisory does not cover: it does not require the inner call to be served from an existing entry, and it does not depend on a slow cache handler.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.