Skip to main content
Security and Infrastructure

VS Code 1.145.3 fixes three MCP flaws that can run commands

Microsoft released Visual Studio Code 1.145.3 on November 10, 2026, fixing three flaws in the editor's MCP client. All three affect version 1.145.2 and earlier. A connected or installed malicious MCP server could reach command execution with the user's permissions.

  • Nov 16, 2026
  • 2 min read
  • LabForty AI Newsroom
VS Code 1.145.3 fixes three MCP flaws that can run commands

Microsoft published three security advisories for Visual Studio Code on November 10, 2026 and released version 1.145.3 the same day. The 1.145 release notes say the update addresses these security issues. All three advisories say versions before 1.145.3 are affected, including 1.145.2.

CVE-2026-120779, tracked as GHSA-66hq-jw93-462h, is in the fallback notification path for MCP elicitation requests. Server-controlled message content could be treated as a clickable VS Code command link. A malicious connected MCP server could cause command execution if the user activated the crafted notification. The advisory rates it High. Its CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, which scores 9.6. The fix renders elicitation messages as literal text and validates the request before display.

CVE-2026-114171, tracked as GHSA-crhv-2887-p3xr and also rated High, covers crafted MCP installation links. A link could include unsafe input definitions or variable values that were not rejected before installation. If installed, those values could cause VS Code to resolve a command-backed input and run a command with the user's permissions. The attacker must get the user to open the link and approve the installation. The fix validates install-link inputs, rejects unsupported command-backed variables and makes the configuration being installed more explicit.

CVE-2026-119983, tracked as GHSA-4x35-6qr8-ww48 and rated High, is in the legacy SSE transport of the MCP client. A remote server could supply a new transport endpoint that VS Code used without sufficiently validating origin and protocol, so follow-up requests could go to an unintended destination and potentially expose credentials or enable further code execution. The fix validates server-provided SSE endpoints before the follow-up transport is established.

Until the update is installed, Microsoft says to connect only to trusted MCP servers, not to open untrusted vscode:mcp/install links, to review the displayed server configuration before approving installation, and to disable or remove affected legacy SSE servers, preferring a trusted transport.

Why this matters

MCP servers now sit inside the editor with the same rights as the developer. A notification, an install link or a legacy transport redirect was enough to turn that trust into a command. Teams should move to 1.145.3, then audit which MCP servers are connected and how they were installed.

Sources: advisory GHSA-66hq-jw93-462h, advisory GHSA-crhv-2887-p3xr, advisory GHSA-4x35-6qr8-ww48, VS Code 1.145 release notes.

This article is not legal advice.

Where every detail matters

Where every detail matters

At LabForty, we develop high-quality websites with a strong focus on detail - from architecture and user experience to business logic.