Skip to main content
CVE-2026-119350VulnerabilityPublished

Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params

Affects nextSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119350· Medium 6.3

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

Data as of 19 Nov 2026, 23:07 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:N/VI:L/VA:L/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 19 Nov 2026.

What to do

Upgrade next to 16.4.5.

Affected software

ProductAffectedFixed in
npmnextAffected
  • >=16.4.0 <16.4.5
Fixed in
  • 16.4.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Next.js to version 16.4.5 or later, where this vulnerability is fixed. As a workaround, set 'partialPrefetching: true' in next.config.js to avoid the cache poisoning behavior. No other actions are required.

Description

Next.js versions 16.4.0 through 16.4.4, when self-hosted with cacheComponents enabled and partialPrefetching disabled, are vulnerable to cache poisoning of shared fallback shells via request-supplied placeholder route parameters. An unauthenticated attacker can poison the fallback shell cache entry shared by a family of routes, causing persistent 404 responses or incorrect parameter rendering in server-side HTML. No script injection or data disclosure occurs. The issue is fixed in version 16.4.5.

References

Community reviews

Loading reviews…