Read the docs
TI-2026-65940 Aliases CVE-2026-94486GHSA-39w2-rjm5-chcv

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

Priority LOW 11CWE-346Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Passive
Attack complexity
Low
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
Low · Low · None
Fix status
Partial Red Hat: 6 without a fix

Attack profile from CVSS 4.0 · CNA. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-346.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00114 1st percentileScored 2026-11-07
Fix Partial next.js (vercel): 16.3.8next (npm): 16.3.8Red Hat: 6 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
vercelnext.js16.0.0 to before 16.3.816.3.8Patch availableCNA
—next (npm)16.0.0 to before 16.3.816.3.8Patch availableGHSA-39w2-rjm5-chcv
  • next.js Vendorvercel Affected 16.0.0 to before 16.3.8 Fixed in 16.3.8 Patch available CNA
  • next (npm) Vendor— Affected 16.0.0 to before 16.3.8 Fixed in 16.3.8 Patch available GHSA-39w2-rjm5-chcv

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*16.0.0 to before 16.3.8Vulnerablevercel
  • cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* Versions 16.0.0 to before 16.3.8 Vulnerable ·vercel

Remediation

  • Fix · CNA next.js (vercel) Fixed in 16.3.8
  • Fix · GHSA-39w2-rjm5-chcv next (npm) Fixed in 16.3.8 Advisory →

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Enterprise Linux 10AffectedNo fix yet: Fix deferred
Red Hat Enterprise Linux 7AffectedNo fix yet: Fix deferred
Red Hat Enterprise Linux 8AffectedNo fix yet: Fix deferred
Red Hat Enterprise Linux 9AffectedNo fix yet: Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3AffectedNo fix yet: Fix deferred
Red Hat Trusted Artifact SignerAffectedNo fix planned: Out of support scope

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-94486
  2. 2026-10-05 CVSS score added · NVD
  3. 2026-10-07 Alias added: GHSA-39w2-rjm5-chcv
  4. 2026-10-07 Fix available: npm/[email protected] · GHSA-39w2-rjm5-chcv
  5. 2026-10-07 CVSS score added · GHSA-39w2-rjm5-chcv
  6. 2026-10-07 Weakness changed · GHSA-39w2-rjm5-chcv
  7. 2026-10-07 5 new references · GHSA-39w2-rjm5-chcv

References

  • TI-2025-34861 Deserialization of untrusted data in Meta react-server-dom-webpack KEVCVSS 3.1CRITICAL 10.0
  • TI-2025-21309 Authorization Bypass in Next.js Middleware CVSS 3.1CRITICAL 9.1
  • TI-2025-34863 Deserialization of untrusted data in Meta react-server-dom-webpack CVSS 3.1HIGH 7.5
  • TI-2024-31371 Cache Poisoning in next.js CVSS 3.1HIGH 7.5
  • TI-2023-24914 Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch… CVSS 3.1HIGH 7.5
  • TI-2026-32490 Next.js: Server-side request forgery in applications using WebSocket upgrades CVSS 3.1HIGH 8.6
See all 62 →

Sources