Skip to main content
VulnerabilityPublished

CVE-2026-119351: vercel next.js · Race Condition

Affects vercel next.jsSource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 6.3 Medium : upgrade to 16.4.5 when convenient.

Data as of 16 Nov 2026, 18:52 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.06.3
Patch
Available – fixed in 16.4.5
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
vercelnext.jsAffected
  • >=16.2.0 <16.4.5
Fixed in
  • 16.4.5

AI-suggested

Upgrade Next.js to version 16.4.5 or later, where this race condition vulnerability is fixed. No other mitigation is required as the issue is resolved by the official patch.

Description

A race condition vulnerability (CWE-362) exists in Next.js versions 16.2.0 through 16.4.4 when Cache Components are enabled. This flaw allows reuse of an outer 'use cache' entry across different root param values, potentially causing cached data to be served incorrectly across requests. The issue arises because React Flight may deliver partial results before nested cache dependencies finish, leading to cache entries that ignore invalidation and lifetime rules. The leaked cached value is not attacker controlled but depends on timing. This vulnerability is fixed in Next.js version 16.4.5.

References

Community reviews

Loading reviews…