Bug 2544647 (CVE-2026-103004) - CVE-2026-103004 next: Next.js: Information disclosure via cache key omission in nested cache handlers
Summary: CVE-2026-103004 next: Next.js: Information disclosure via cache key omission ...
Keywords:
Status: NEW
Alias: CVE-2026-103004
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2558245 2558848 2558849 2558850 2558854 2558846 2558852
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-01 15:03 UTC by OSIDB Bzimport
Modified: 2026-10-22 11:07 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-01 15:03:35 UTC
Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return value to pages with different root params. 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.

This has been patched in 16.3.8.


Note You need to log in before you can comment on or make changes to this bug.