Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Session Fixation / Privilege Escalation in Visual Studio Code MCP One-Click Installer

IdentifiersCVE-2026-41613CWE-384· Session Fixation

CVE-2026-41613 is an elevation of privilege vulnerability in Microsoft Visual Studio Code affecting the one-click installer flow for Model Context Protocol (MCP) servers. According to the provided reporting, the installer preview dialog displayed only a subset of the configuration fields while silently accepting additional hidden fields, including environment variables and HTTP headers. This UI trust-boundary failure allowed a malicious MCP install link or malicious file opened in VS Code to present an apparently benign installation prompt while injecting unseen configuration. One exploitation path abused hidden environment-variable injection, specifically NODE_OPTIONS, together with Node.js --import support for data URLs, to preload attacker-controlled JavaScript before the MCP server started; that JavaScript could then execute shell commands permitted by the host OS. A second path abused hidden HTTP headers so the MCP server authenticated using attacker-supplied credentials, causing subsequent assistant actions to execute within the attacker-controlled session. Microsoft classifies the issue as session fixation and associates it with Visual Studio Code privilege escalation over a network.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can give an attacker the permissions associated with the targeted MCP server's managed identity or otherwise cause VS Code-integrated MCP activity to run in an attacker-controlled session. In the environment-variable injection path, this can lead to arbitrary JavaScript execution prior to MCP server startup and subsequent OS command execution, enabling compromise of the developer workstation, persistence via workspace settings, remote access/backdoor installation, and high confidentiality, integrity, and availability impact. In the session-fixation/header-injection path, the attacker can cause the developer's AI assistant actions—such as reading files, sending messages, or querying connected services—to occur under attacker-supplied credentials, potentially exposing or modifying resources reachable by that identity. Microsoft states this does not inherently grant broader tenant-wide or administrator permissions beyond those of the affected managed identity.

Mitigation

If you can’t patch tonight, do this now.

Until patched versions are fully deployed, restrict or disable use of one-click MCP server installation links where feasible, and avoid opening untrusted files or workspaces in VS Code. Treat MCP installation prompts as untrusted input and manually inspect workspace settings and MCP server configuration for unexpected environment variables, NODE_OPTIONS values, environment file paths, or custom HTTP headers. Limit the privileges granted to MCP server managed identities and connected service accounts so that compromise yields minimal access. Where operationally possible, constrain outbound connectivity and monitor for suspicious MCP server launches, unexpected Node.js child process behavior, or persistence in workspace settings.

Remediation

Patch, then assume compromise.

Apply Microsoft's fix for CVE-2026-41613 in Visual Studio Code. The provided content states Microsoft patched the issue by rendering previously hidden installation parameters—including environment variables, environment file paths, and HTTP headers—in the install preview so users can review the full MCP server configuration before approval. Organizations should update VS Code to a version containing the May 2026 fix and review existing workspace settings for previously installed MCP server configurations that may contain unexpected environment variables, headers, or persistence mechanisms.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationVisual Studio Codeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.