Advisory

GHSA-h694-7cp9-m8p3

Also known as: CVE-2026-103004

Summary

next.js cache leak across root param values in nested 'use cache' functions

Details

Impact

With Cache Components enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function's cache key then omits that root param. The enclosing 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 — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further.

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

Workarounds

There are no known workarounds. Apps should upgrade to the patched version as soon as possible.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-10-22 16:08 UTC
Modified
2026-10-22 16:30 UTC

Affected packages and fixes

next

npm · All systems

Affected

  • introduced 16.3.0, fixed 16.3.8 (semver)

Fixed versions

16.3.8

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences