CVE-2026-119349: vercel next.js · Use of Multiple Resources with Duplicate Identifier
Affects vercel next.jsSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 16.4.5 when convenient.
Data as of 16 Nov 2026, 19:04 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 16.4.5
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade vercel next.js to 16.4.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vercelnext.js | Affected
| Fixed in
|
AI-suggested
Upgrade Next.js to version 16.4.5 or later, where this issue is fixed. No other mitigation is indicated or required.
Description
Next.js versions from 16.0.0 up to but not including 16.4.5 contain a vulnerability where applications using the App Router and passing binary arguments to functions with the 'use cache' directive can generate identical cache keys for different arguments. This leads to cross-user data disclosure or cache poisoning. The issue is fixed in version 16.4.5.
References
- github.com/vercel/next.js/security/advisories/GHSA-rhh4-g77r-r9qj (opens in a new tab)
- github.com/vercel/next.js/commit/6596840a0fa3c2633735b05e41ca3d9ab01ece41 (opens in a new tab)
- github.com/vercel/next.js/releases/tag/v16.4.5 (opens in a new tab)
- nextjs.org/blog/november-2026-security-release (opens in a new tab)