Skip to main content
VulnerabilityPublished

CVE-2026-94486: vercel next.js · Origin Validation Error

Affects vercel next.jsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.3 Low : upgrade to 16.3.8 when convenient.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 16.3.8
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 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 next.js and next to 16.3.8.

Affected software

ProductAffectedFixed in
vercelnext.jsAffected
  • >=16.0.0 <16.3.8
Fixed in
  • 16.3.8
npmnextpkg:npm/nextOther threatsAffected
  • >=16.0.0 <16.3.8
Fixed in
  • 16.3.8

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.3.8 or later to apply the official fix. Since the vulnerability only affects the development server and not production deployments, ensure that development servers are not exposed to untrusted networks or accessed via untrusted websites. Patch status is confirmed fixed in 16.3.8.

Description

Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, the next dev development server exposes a Model Context Protocol endpoint without reliably restricting cross-site requests. A malicious website visited by a developer can reach the endpoint and read the project's disk location, source code snippets from error reports, route inventory, and development logs. Production deployments do not serve this endpoint. This issue is fixed in version 16.3.8.

References

Community reviews

Loading reviews…