Skip to main content
Vulnerability Database/CVE-2026-94486

CVE-2026-94486: Vercel Next.js Information Disclosure Flaw

CVE-2026-94486 is an information disclosure vulnerability in Vercel Next.js that exposes sensitive development data through an unrestricted endpoint. This article covers the technical details, affected versions, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-94486 Overview

CVE-2026-94486 is an origin validation vulnerability [CWE-346] in Vercel Next.js versions 16.0.0 through 16.3.7. The next dev development server exposes a Model Context Protocol (MCP) endpoint without reliably restricting cross-site requests. A malicious website visited by a developer can reach the local MCP endpoint and extract project disk paths, source code snippets from error reports, route inventory, and development logs. Production deployments are not affected because the endpoint is not served outside development mode. The issue is fixed in Next.js 16.3.8.

Critical Impact

A developer visiting a malicious page while running next dev can leak project paths, source snippets, routes, and development logs to a remote attacker through DNS rebinding against the local MCP endpoint.

Affected Products

  • Vercel Next.js 16.0.0 through 16.3.7 (development server only)
  • Node.js-based Next.js installations running next dev
  • Not affected: production builds and deployments

Discovery Timeline

  • 2026-10-02 - CVE-2026-94486 published to NVD
  • 2026-10-05 - Last updated in NVD database
  • Fix released - Next.js version 16.3.8 includes the MCP middleware patch

Technical Details for CVE-2026-94486

Vulnerability Analysis

The next dev command starts a local HTTP server that hosts a Model Context Protocol endpoint for AI tooling integration. The MCP middleware did not consistently validate the request origin or host header against an allowlist. An attacker-controlled website loaded in the developer's browser can issue requests that reach the local endpoint through techniques such as DNS rebinding.

The exposed MCP endpoint returns internal development data including the project's absolute disk location, excerpts of source code embedded in error reports, the full route inventory, and recent development logs. This information supports reconnaissance against the developer's workstation and the application under development.

Root Cause

The root cause is missing or incomplete origin validation on the MCP middleware [CWE-346]. The CSRF-style protections applied elsewhere in the dev server were not consistently applied to the MCP route, allowing cross-site requests to be processed as if they were legitimate local tool calls.

Attack Vector

Exploitation requires that a developer run next dev locally and visit a malicious website in the same browser session. The attacker hosts a page that performs DNS rebinding or exploits permissive origin handling to send requests to http://localhost:<port> MCP routes. Successful requests return development metadata directly to the attacker's script.

typescript
// Patch excerpt: packages/next/src/server/mcp/get-mcp-middleware.ts
  type McpServerOptions,
} from './get-or-create-mcp-server'
import { parseBody } from '../api-utils/node/parse-body'
+import { parsePath } from '../../shared/lib/router/utils/parse-path'
+import { removeTrailingSlash } from '../../shared/lib/router/utils/remove-trailing-slash'
import { StreamableHTTPServerTransport } from 'next/dist/compiled/@modelcontextprotocol/sdk/server/streamableHttp'

export function getMcpMiddleware(options: McpServerOptions) {
// Source: [vercel/next.js commit 2d9f50a](https://github.com/vercel/next.js/commit/2d9f50a409312696145b82b3157aadb6b1fef476)

The companion change in packages/next/src/server/lib/router-utils/block-cross-site-dev.ts reuses isCsrfOriginAllowed and parsePath to enforce origin checks on the MCP route, closing the DNS rebinding gap.

Detection Methods for CVE-2026-94486

Indicators of Compromise

  • Outbound HTTP requests from a developer workstation to localhost MCP paths originating from a browser tab on an untrusted domain.
  • Unexpected Host header values on local dev server requests that do not match localhost or 127.0.0.1.
  • Browser console or network logs showing cross-origin fetches targeting next dev ports (commonly 3000) with MCP route segments.

Detection Strategies

  • Inspect next dev access logs for requests to MCP endpoints with Origin or Referer headers pointing to external domains.
  • Monitor developer endpoints for DNS responses that resolve attacker-controlled hostnames to 127.0.0.1 or RFC1918 addresses, a hallmark of DNS rebinding.
  • Review installed Next.js versions across developer workstations and flag any instance in the 16.0.0–16.3.7 range.

Monitoring Recommendations

  • Enable endpoint telemetry on developer machines to capture local HTTP server traffic alongside the parent browser process.
  • Alert on node processes serving dev ports that receive requests from non-loopback origins.
  • Track Next.js dependency versions in CI and software composition analysis tooling to detect vulnerable releases.

How to Mitigate CVE-2026-94486

Immediate Actions Required

  • Upgrade Next.js to version 16.3.8 or later across all development environments.
  • Audit developer workstations for the vulnerable version range and prioritize updates where next dev is routinely used.
  • Instruct developers to avoid browsing untrusted sites in the same browser profile used while next dev is running.

Patch Information

The fix is delivered in Next.js 16.3.8. The patch introduces consistent origin validation on the MCP middleware using isCsrfOriginAllowed, parsePath, and removeTrailingSlash to normalize and verify request paths and origins. See the GitHub Security Advisory GHSA-39w2-rjm5-chcv, the patch commit 2d9f50a, and the Next.js v16.3.8 release notes.

Workarounds

  • Bind the dev server to 127.0.0.1 only and block external DNS resolution to loopback at the host firewall.
  • Configure allowedDevOrigins in next.config.js to explicitly restrict acceptable origins for the dev server.
  • Run next dev inside an isolated browser profile or container that is not used for general web browsing.
bash
# Upgrade Next.js to the patched release
npm install next@16.3.8

# Verify installed version
npx next --version

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.