Microsoft published a VS Code security advisory on 10 November 2026 describing a code execution vulnerability in the fallback notification path for Model Context Protocol (MCP) elicitation requests. The advisory, GHSA-66hq-jw93-462h, lists versions before 1.145.3 as affected and 1.145.3 as patched. It assigns the issue CVE-2026-120779 and a High severity rating with a CVSS score of 8.3.[1]

According to the advisory, server-controlled message content could be interpreted as an interactive VS Code command link. A malicious MCP server could thereby cause command execution if a user activated the crafted notification. The stated prerequisites are control of a connected MCP server and persuading the user to click the malicious link; the described attack requires user interaction.[1]

Microsoft says the fix, available starting with VS Code 1.145.3, renders elicitation messages as literal text and validates the request payload before displaying it. The advisory identifies patches 305e248 and e3a4962. Its workarounds are to connect only to trusted MCP servers and avoid activating notification links produced by an untrusted server.[1]

[1]: Microsoft, “Remote Code Execution via MCP Elicitation Notifications,” published 10 November 2026. https://github.com/microsoft/vscode/security/advisories/GHSA-66hq-jw93-462h

Sources

  1. Remote Code Execution via MCP Elicitation Notificationsgithub.com · 10 Nov 2026

Check or correct this page

Verification record

The digest below shows whether the text you are reading matches the published source. It does not show that the reporting is correct. The build computes it from this page's Markdown source and lists it in the site manifest.

5bf5ee5b374944037c3539da57adfd8d6906115ce832686b6e4d48ce94e7dc4a