Skip to main content
Menu
CVEs

CVE

Next.js cross-user cache disclosure and poisoning in use cache

CVE-2026-119349EUVD-2026-126594

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

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 16.4.5
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 16.4.5.

Published
Last modified
Reference
Last checked
40/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Next.js, a React framework for building web applications, has a flaw in its App Router "use cache" feature: functions that receive binary arguments such as Uint8Array or Blob values can produce the same cache key for different inputs. A remote attacker without logging in could then read cached data belonging to other users or poison results served to them.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

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.

cve.now Index

40Pcve.now Index 40 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach17/20Affects Next.js (a widely deployed server, runtime, framework or database)
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 85 if added to CISA KEV
  • Would score about 80 if CISA's SSVC rates exploitation active
  • Would score about 45 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 16.4.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-119349 (Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-119349 (entry last updated 2026-11-16):
Affected:
- vercel next.js: from 16.0.0, fixed in 16.4.5
Fixed versions: 16.4.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-119349 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119349 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/vercel/next.js/security/advisories/GHSA-rhh4-g77r-r9qj
- https://github.com/vercel/next.js/commit/6596840a0fa3c2633735b05e41ca3d9ab01ece41
- https://github.com/vercel/next.js/releases/tag/v16.4.5
- https://nextjs.org/blog/november-2026-security-release
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-119349
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119349"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • vercel next.js

    From 16.0.0 · fixed in 16.4.5

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Repository
  2. Repository
  3. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-119349

Is CVE-2026-119349 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-119349?

next.js: from 16.0.0 before 16.4.5.Source: cve.now feed data

How do I fix CVE-2026-119349?

Upgrade to a fixed version: 16.4.5.Source: cve.now feed data