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

Published Nov 16, 2026
·
Updated

Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.4.5, Next.js App Router applications that pass binary arguments, such as Uint8Array or Blob values, to functions using the 'use cache' directive can generate identical cache keys for distinct arguments. Requests with different binary arguments can therefore share a cached result, causing cross-user disclosure of cached data or allowing one request to poison results returned to another user. This issue is fixed in version 16.4.5.

Affected Software

1 affected component
npm/next>=16.0.0<16.4.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.4.5

Event History

Nov 16, 2026
CVE Published
via MITRE·06:39 PM
Data Sourced
via MITRE·06:39 PM
DescriptionWeakness

Frequently Asked Questions

1

Which applications are exposed to this issue?

Applications using the Next.js App Router and the 'use cache' directive are affected only when cached functions receive binary arguments such as Uint8Array or Blob values. The affected version range is 16.0.0 through 16.4.4.

2

What must an attacker be able to do to exploit the issue?

An attacker must be able to cause requests with distinct binary argument values to reach a function using 'use cache'. Colliding cache keys can then cause the attacker’s request to receive another user’s cached result or influence the result later returned to another user.

3

Is a default Next.js deployment affected?

Not solely by using Next.js. Exposure depends on using the App Router, using 'use cache', and passing binary values to cached functions.

4

How can this be mitigated if upgrading is not immediately possible?

Avoid passing binary arguments, including Uint8Array or Blob values, to functions using the 'use cache' directive. Use cache inputs that do not rely on binary argument values until the application can be updated.

5

How can I remediate the vulnerability?

Upgrade Next.js to version 16.4.5, which fixes the issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203