---
title: "GHSA-rhh4-g77r-r9qj: Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments"
description: "Moderate severity. Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments. Affects next; fixed in 16.4.5."
url: https://inlinr.com/advisories/GHSA-rhh4-g77r-r9qj
lang: en
---

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

Moderate Vulnerability GHSA-rhh4-g77r-r9qj CVE-2026-119349 Published 19 Nov 2026

# Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments

Your version 

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

- 16.x 16.0.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 – 15.5.29  
379 releases
2. Affected

16.0.0 – 16.4.4  
47 releases
3. Fixed

16.4.5 – 16.4.6  
2 releases

428 stable releases of next, oldest to newest.

## What happens

Next.js App Router applications that pass binary arguments (such as Uint8Array or Blob values) to functions using the `use cache` directive can produce identical cache keys for distinct arguments, allowing cached results to be shared across users — cross-user disclosure of cached data or cache poisoning. This affects applications using `use cache` with binary arguments.

## How it is exploited

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

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

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

## References

- [Reference](https://github.com/vercel/next.js/security/advisories/GHSA-rhh4-g77r-r9qj "https://github.com/vercel/next.js/security/advisories/GHSA-rhh4-g77r-r9qj")  
github.com/vercel/next.js/security/advisories/G…
- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-119349 "https://nvd.nist.gov/vuln/detail/CVE-2026-119349")  
nvd.nist.gov/vuln/detail/CVE-2026-119349
- [Fix commit](https://github.com/vercel/next.js/commit/6596840a0fa3c2633735b05e41ca3d9ab01ece41 "https://github.com/vercel/next.js/commit/6596840a0fa3c2633735b05e41ca3d9ab01ece41")  
6596840
- [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.
