Skip to main content
VulnerabilityPublished

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

Affects vercel next.jsSource CVE Database V5

0
Compare

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

Data as of 16 Nov 2026, 18:37 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.3.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. Avoid nesting 'use cache' inside unstable_cache(), as this raises an unsupported-operation error and prevents the issue. No other mitigations are indicated.

Description

Next.js versions from 16.3.0 up to but not including 16.4.5 contain a race condition vulnerability in the use of the 'use cache' function combined with unstable_cache(). This flaw can cause cached data to be incorrectly shared across different root parameters during concurrent requests, potentially leading to data disclosure. The issue arises during the first cache fill after a cold start, where concurrent requests can receive cached results meant for different parameters. The vulnerability is fixed in version 16.4.5.

References

Community reviews

Loading reviews…