CVE-2026-41611: Microsoft Visual Studio Code XSS Vulnerability

CVE-2026-41611 Overview

CVE-2026-41611 is a cross-site scripting (XSS) vulnerability in Microsoft Visual Studio Code. The flaw stems from improper neutralization of script-related HTML tags in a web page rendered by the editor. An unauthorized attacker can execute code locally when a user interacts with attacker-controlled content. Exploitation requires user interaction and local access, which limits the practical attack surface. Microsoft has documented the issue and released remediation guidance through the Microsoft Security Response Center.

Critical Impact

An attacker can execute code in the context of the Visual Studio Code user after the user opens or interacts with malicious content containing unsanitized script tags.

Affected Products

• Microsoft Visual Studio Code

Discovery Timeline

• 2026-05-12 - CVE-2026-41611 published to NVD
• 2026-05-15 - Last updated in NVD database

Technical Details for CVE-2026-41611

Vulnerability Analysis

The vulnerability is classified under [CWE-79] Improper Neutralization of Input During Web Page Generation and [CWE-77] Improper Neutralization of Special Elements used in a Command. Visual Studio Code renders web content within its Electron-based interface using webviews and HTML components. When script-related HTML tags are not properly neutralized, attacker-supplied markup can execute within the rendering context.

The EPSS score is 0.035% with a percentile of 10.451, indicating low observed exploitation likelihood. No public proof-of-concept code is available, and the vulnerability is not listed on the CISA Known Exploited Vulnerabilities catalog.

Root Cause

The root cause is inadequate sanitization of HTML input rendered by Visual Studio Code. Script-related tags such as <script> and event handler attributes are not stripped or escaped before being inserted into the document. This allows arbitrary JavaScript to execute within the editor's rendering context, which has elevated privileges compared to a browser sandbox.

Attack Vector

The attack vector is local and requires user interaction. An attacker must deliver a crafted file, extension, workspace, or markdown preview containing malicious HTML to the target. When the victim opens the content in Visual Studio Code, the embedded script executes locally. Common delivery methods include malicious repositories, untrusted workspace folders, and crafted markdown or notebook files shared through collaboration channels.

No verified exploitation code is publicly available. See the Microsoft Security Update for CVE-2026-41611 for vendor technical details.

Detection Methods for CVE-2026-41611

Indicators of Compromise

• Markdown, HTML, or notebook files containing unexpected <script> tags or inline event handlers such as onerror and onload.
• Visual Studio Code spawning unexpected child processes such as cmd.exe, powershell.exe, or /bin/sh shortly after opening a workspace or file.
• Outbound network connections initiated by Code.exe to untrusted hosts following preview rendering of untrusted content.

Detection Strategies

• Inspect repositories and shared workspaces for HTML payloads embedded in markdown previews, README files, and notebook cells.
• Monitor process lineage where Visual Studio Code is the parent of scripting interpreters or LOLBins.
• Correlate file open events in Visual Studio Code with subsequent file system writes to user profile or autostart directories.

Monitoring Recommendations

• Enable endpoint logging for child process creation under Code.exe and equivalent binaries on macOS and Linux.
• Track installation and update events for Visual Studio Code extensions, especially those sourced outside the official marketplace.
• Alert on Visual Studio Code processes making outbound network connections immediately after opening a new workspace.

How to Mitigate CVE-2026-41611

Immediate Actions Required

• Apply the security update referenced in the Microsoft Security Update for CVE-2026-41611 advisory.
• Verify that auto-update is enabled in Visual Studio Code to receive future security patches without delay.
• Educate developers to avoid opening untrusted repositories, notebooks, and workspaces without enabling Workspace Trust restrictions.

Patch Information

Microsoft has published guidance and update information for CVE-2026-41611 through the Microsoft Security Response Center. Refer to the Microsoft Security Update for CVE-2026-41611 for the fixed version and deployment instructions. Update Visual Studio Code to the latest released version on all developer endpoints.

Workarounds

• Enable Workspace Trust and open untrusted folders in Restricted Mode to limit code execution from workspace content.
• Disable markdown preview and notebook rendering for files originating from untrusted sources until patches are applied.
• Restrict installation of third-party extensions through enterprise policy and review existing extensions for unnecessary HTML rendering capabilities.

# Configuration example: enforce Workspace Trust via settings.json
{
  "security.workspace.trust.enabled": true,
  "security.workspace.trust.startupPrompt": "always",
  "security.workspace.trust.untrustedFiles": "prompt",
  "extensions.autoCheckUpdates": true,
  "update.mode": "default"
}