Skip to content

NEWS, 10 NOV 2026, read 12 Nov 2026

VS Code 1.145.3 fixes MCP client and agent host code execution flaws

All newsSee the full index

On 10 Nov 2026 the VS Code repository published several advisories affecting versions 1.145.2 and earlier, all fixed in 1.145.3. Three involve the MCP client. In the legacy SSE transport, a remote server could supply a follow-up endpoint that VS Code used without validating origin and protocol (GHSA-4x35-6qr8-ww48). A malicious server could also put a clickable command link in an elicitation notification (GHSA-66hq-jw93-462h, High 8.3). A crafted MCP install link could carry command-backed input values (GHSA-crhv-2887-p3xr).

A fourth, GHSA-w9fm-7vcm-cvq4, is a security feature bypass in the Agent Host. Local-command syntax in an agent message could be treated as if the user typed it and run without the expected terminal approval. The advisory says the attacker must influence an agent's child prompt, typically through untrusted repository instructions, and the user must grant the related session tool operation.

Each one needs some user action or a hostile MCP server, and the advisories list workarounds: connect only to trusted MCP servers, keep terminal approvals on, and avoid session-wide tool grants in repositories with untrusted instructions. Together they show that the MCP client and the agent loop in an IDE are now part of the attack surface.

What to check: VS Code version on managed laptops (1.145.3 or later), the list of MCP servers configured in developer profiles, and whether policy blocks session-wide approvals.

Earlier and later in the release log

Every dated item is on the release log. Seen a release this log missed? Send a tip.

Sources

  1. github.com, read 12 Nov 2026

Last reviewed 12 Nov 2026.