CVE-2026-94486 vercel CVE debrief

Who should care

Developers using Next.js development server (`next dev`) should assess exposure and take remediation steps. This includes verifying development environments, prioritizing upgrades to version 16.3.8 or later, and monitoring logs for suspicious activity. Operators and security teams responsible for Next.js deployments should also review and address potential exposure.

Why it matters

CVE-2026-94486 allows information disclosure in Next.js development server's Model Context Protocol endpoint. Defenders should verify development environments, prioritize upgrading to version 16.3.8 or later, and monitor logs for suspicious activity.

• Sensitive development data, including project location on disk, source code snippets, route inventory, and development logs, may be accessed by malicious websites.
• Development environments are at risk of information disclosure.
• Verification of development environment configurations and upgrade to fixed versions are necessary.

Technical summary

The Next.js development server exposes a Model Context Protocol endpoint that does not verify which website a request originates from, allowing a malicious website visited by the developer to read sensitive development data. This includes project location on disk, source code snippets, route inventory, and development logs. Only applications run with `next dev` are affected; production deployments do not serve this endpoint. Defenders should prioritize verifying development environments for exposure and upgrading to version 16.3.8 or later.

Defensive priority

Defenders should prioritize verifying development environments for exposure and upgrading to version 16.3.8 or later.

Recommended defensive actions

• Verify development environments for exposure to the Model Context Protocol endpoint.
• Upgrade to version 16.3.8 or later of Next.js.
• Monitor development logs for suspicious activity.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and source item provide details on the vulnerability in Next.js development server's Model Context Protocol endpoint. Evidence is limited to public sources and may not be comprehensive. Defenders should verify development environments for exposure and review available information to assess potential impact. Additional verification and review of development logs may be necessary.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.