Bug 2544647 (CVE-2026-103004)

Summary: CVE-2026-103004 next: Next.js: Information disclosure via cache key omission in nested cache handlers
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: bbrownin, eborisov, gotiwari, jhorak, kaycoth, lball, mvyas, ngough, rhel-process-autobot, veshanka, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Next.js. This vulnerability may lead to information disclosure when nested caching features fail to properly include root parameters in their cache keys. An unauthenticated remote user can receive cached application responses intended for a different user or request context. This occurs because the application reuses a single cached entry across requests with differing parameters, potentially allowing intermediate caches to further redistribute the exposed data.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2558245, 2558848, 2558849, 2558850, 2558854, 2558846, 2558852    
Bug Blocks:    

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.