---
title: "GHSA-mfr8-8qww-v76h: Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()"
description: "Moderate severity. Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()."
url: https://inlinr.com/advisories/GHSA-mfr8-8qww-v76h
lang: en
---

[Packages](https://inlinr.com/packages) / [next](https://inlinr.com/packages/next) / [Security](https://inlinr.com/packages/next/security)

Moderate Vulnerability GHSA-mfr8-8qww-v76h CVE-2026-119790 Published 16 Nov 2026

# Next.js: Information disclosure across root params when a 'use cache' function is called through unstable\_cache()

Your version 

Affected releases · [next](https://inlinr.com/packages/next)

- 16.x 16.3.0 – 16.4.4 Fixed 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.2.12  
412 releases
2. Affected

16.3.0 – 16.4.4  
14 releases
3. Fixed

16.4.5 – 16.4.6  
2 releases

428 stable releases of next, oldest to newest.

## What happens

Next.js applications with `'use cache'` can disclose cached data across root params when the same `'use cache'` function is called both directly during rendering and through `unstable_cache()`, and that function reads a root param. Root params are route parameters of the root layout, and applications commonly use them to scope data, for example per locale.

During a cold process start, a cross-request deduplication race allowed an `unstable_cache()` call to join the in-flight fill of a concurrent direct call and receive its result, bypassing the root param check that would normally reject it. `unstable_cache()` then stored that result under a cache key without root params, so subsequent requests for other root param values received the same entry until it is revalidated or evicted. Cached data produced for one root param value is returned to requests for other values.

Exploitation requires the `unstable_cache()` request to arrive while the function's first fill after a process start is still in flight. Outside this race, the nesting already throws an error: `'use cache' inside unstable_cache() is unsupported`, and avoiding it is a complete workaround.

## How it is exploited

Exploitable over the network, with no account and no action from a user.

- **Confidentiality**: low
- **Integrity**: none
- **Availability**: none

CVSS:4.0/​AV:N/​AC:L/​AT:P/​PR:N/​UI:N/​VC:L/​VI:N/​VA:N/​SC:N/​SI:N/​SA:N

## References

- [Reference](https://github.com/vercel/next.js/security/advisories/GHSA-mfr8-8qww-v76h "https://github.com/vercel/next.js/security/advisories/GHSA-mfr8-8qww-v76h")  
github.com/vercel/next.js/security/advisories/G…
- [Fix commit](https://github.com/vercel/next.js/commit/d605874e5a4b8b6b7dca1b6e07bcabb44d0e2e5b "https://github.com/vercel/next.js/commit/d605874e5a4b8b6b7dca1b6e07bcabb44d0e2e5b")  
d605874
- [Package](https://github.com/vercel/next.js "https://github.com/vercel/next.js")  
github.com/vercel/next.js
- [Reference](https://github.com/vercel/next.js/releases/tag/v16.4.5 "https://github.com/vercel/next.js/releases/tag/v16.4.5")  
github.com/vercel/next.js/releases/tag/v16.4.5
- [Reference](https://nextjs.org/blog/november-2026-security-release "https://nextjs.org/blog/november-2026-security-release")  
nextjs.org/blog/november-2026-security-release

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
