vercel · Next.js · published 2026-11-16

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

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-119350 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 12% of all CVEs. This Next.js vulnerability: CVSS 6.3 (v4.0). Fixed upstream in Next.js 16.4.5, 15.5.29. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Next.js 16.4.5, 15.5.29.

Patch events

  1. This monthSecurity release

    Web frameworkNext.js

    Next.js security releases: 16.4.5, 15.5.29

    Upgrade to 16.4.515.5.29

    Why: Vendor security release for server software (most severe: CVE-2026-119347).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (13th pct)FIRST EPSS v2026.06.15
CVSS base score6.3 (v4.0)
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
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Next.js is a React framework for building full-stack web applications. From 16.4.0 until 16.4.5, self-hosted Next.js applications served with next start can allow an unauthenticated request to poison a shared fallback shell when cacheComponents is true and partialPrefetching is unset or false. The affected dynamic route must have a prerenderable param declared by generateStaticParams whose requested value was not generated at build time, at least two never-prerenderable params below it, a layout that reads the shallower param inside a Suspense boundary, and a blocking fallback shell. A request-supplied placeholder route param whose path segment equals the percent-encoded bracketed name of its own deeper route param is incorrectly treated as unresolved, while the shallower concrete value is rendered into the shared shell and its HTTP status is persisted. Depending on application behavior, subsequent routes sharing that shell can receive a persistent 404 or attacker-selected substituted param text. Client hydration corrects substituted text, and the issue does not enable markup or script injection or disclose data. This issue is fixed in version 16.4.5.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →