1-minute read
What a defender needs to know
VS Code’s MCP install preview omitted configuration fields that it still saved. A crafted link could hide an environment import that executed when the server started, or an Authorization header that silently routed tool activity through an attacker’s account.
Microsoft fixed CVE-2026-41613 in VS Code 1.119.1. The primary research says Cursor displayed environment variables in its comparison testing, so the confirmed scope here is VS Code rather than every editor named in later coverage.
Update every VS Code endpoint, then inspect workspace mcp.json files for unexpected env, envFile, headers, or cwd values. Prioritize NODE_OPTIONS entries containing --import and pre-populated Authorization headers; correlate findings with child shells and unusual outbound traffic.
Verify that every endpoint is patched and each configuration has an accountable owner. Investigate unexplained launch fields and credentials before completing the review.