vercel · Next.js · published 2026-10-02

CVE-2026-94486Next.js: Information disclosure in the Next.js development server's Model Context Protocol endpoint

Routine No exploitation evidence; EPSS 0.1%.

CVE-2026-94486 is not known to be exploited in the wild. EPSS estimates a 0.1% chance of exploitation in the next 30 days, higher than 3% of all CVEs. This Next.js vulnerability: CVSS 2.3 (v4.0). Fixed upstream in Next.js 16.3.8, 16.3, 15.5. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Next.js 16.3.8, 16.3, 15.5.

Patch events

  1. This monthSecurity release

    Web frameworkNext.js

    Next.js security releases: 16.3.8, 16.3, 15.5

    Upgrade to 16.3.816.315.5

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

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.1% (3th pct)FIRST EPSS v2026.06.15
CVSS base score2.3 (v4.0)
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
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.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.

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 →