Is CVE-2026-94486 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-94486 being exploited in the wild.

How severe is CVE-2026-94486?

Medium severity, with a CVSS score of 5.4, published 2 October 2026.

Which products and versions are affected?

next (npm) >= 16.0.0, < 16.3.8, SEMVER:introduced=16.0.0,fixed=16.3.8; Vercel Next.js 16.0.0 to 16.3.7.

Is there a fix for CVE-2026-94486?

Yes. next (npm): upgrade to 16.3.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-94486 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-94486?

Check whether you run next (npm) or Vercel Next.js at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-94486: Vercel Next.js information disclosure in dev server MCP endpoint

Q: Is there a fix for CVE-2026-94486?

Yes. next (npm): upgrade to 16.3.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-94486 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-94486?

Check whether you run next (npm) or Vercel Next.js at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-94486 · Severity: medium · CVSS 5.4 · Published 2026-10-02

Next.js is a React framework used to build web applications. The development server in versions 16.0.0 through 16.3.7 exposes a Model Context Protocol endpoint that insufficiently restricts cross-site requests. A malicious website visited by a developer can steal sensitive information including the project's disk location, source code snippets, route inventory, and development logs. Production deployments are not affected.

Technologies: next (npm), Vercel Next.js. Vendors: npm, Vercel.

Quick answers

Is CVE-2026-94486 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-94486 being exploited in the wild.
How severe is CVE-2026-94486?: Medium severity, with a CVSS score of 5.4, published 2 October 2026.
Which products and versions are affected?: next (npm) >= 16.0.0, < 16.3.8, SEMVER:introduced=16.0.0,fixed=16.3.8; Vercel Next.js 16.0.0 to 16.3.7.
Is there a fix for CVE-2026-94486?: Yes. next (npm): upgrade to 16.3.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-94486 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-94486?: Check whether you run next (npm) or Vercel Next.js at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

next (npm): upgrade to 16.3.8 or later
```
npm install next@16.3.8
```

Technical details

A cross-site request forgery (CSRF) vulnerability exists in the Next.js development server's Model Context Protocol endpoint, which lacks reliable same-origin protections. An attacker can craft a malicious web page that, when visited by a developer running next dev locally, makes requests to the exposed endpoint via the browser to extract sensitive development information. The vulnerability requires a developer to visit an attacker-controlled website while running the development server; production deployments do not expose this endpoint.

Affected products

Vercel Next.js 16.0.0 to 16.3.7

Identifiers

CVE-2026-94486
GHSA-39w2-rjm5-chcv

Timeline

2026-10-02: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.