CVE-2026-47285: Visual Studio Code RCE Vulnerability

CVE-2026-47285 Overview

CVE-2026-47285 is a command injection vulnerability in Microsoft Visual Studio Code. The flaw stems from improper neutralization of special elements passed to a command interpreter [CWE-77]. An unauthorized attacker can exploit the weakness over a network to disclose sensitive information. Exploitation requires user interaction, meaning the target must open a malicious file, project, or link supplied by the attacker. Successful exploitation impacts confidentiality without affecting integrity or availability of the host system.

Critical Impact
Attackers can execute injected commands within the Visual Studio Code process context to read and exfiltrate sensitive data accessible to the developer, including source code, credentials, and tokens stored in the workspace.

Affected Products

Microsoft Visual Studio Code

Discovery Timeline

2026-08-11 - CVE-2026-47285 published to NVD
2026-08-12 - Last updated in NVD database

Technical Details for CVE-2026-47285

Vulnerability Analysis

The vulnerability is a command injection weakness classified under [CWE-77]. Visual Studio Code fails to properly neutralize special characters before passing input to a downstream command processor. Attacker-controlled content embedded in a project, extension configuration, or workspace file reaches a command execution routine without adequate sanitization. When a user opens the crafted resource, the injected command runs in the editor process context. The result is disclosure of information the developer's session can access, such as environment variables, workspace files, and authentication artifacts.

Root Cause

The root cause is insufficient input validation and command argument neutralization inside Visual Studio Code. Special shell metacharacters or command separators supplied through untrusted project metadata are concatenated into command strings rather than passed as isolated arguments. This allows attacker input to alter the intended command structure and introduce additional commands during editor operations.

Attack Vector

Exploitation follows a network-delivered, user-interaction path. An attacker distributes a malicious repository, workspace, or file via phishing, a public code hosting platform, or a supply-chain vector. When the developer clones the repository and opens it in Visual Studio Code, the crafted content triggers the injected command. Because privileges required are none and complexity is low, any developer opening the malicious project is a viable target. Refer to the Microsoft Security Update CVE-2026-47285 advisory for vendor-specific technical detail.

Detection Methods for CVE-2026-47285

Indicators of Compromise

Unexpected child processes spawned by Code.exe or code invoking shell interpreters such as cmd.exe, powershell.exe, bash, or sh shortly after a workspace is opened.
Outbound network connections initiated by Visual Studio Code or its child processes to previously unseen domains following the opening of an untrusted repository.
Access to credential stores, SSH key directories (~/.ssh), or environment files (.env) by processes descended from the editor.

Detection Strategies

Hunt for Visual Studio Code process trees containing embedded shell metacharacters (;, &&, |, backticks) in command-line arguments.
Correlate workspace open events with subsequent file reads on sensitive paths and network egress within a short time window.
Flag installations or executions of unsigned or unexpected Visual Studio Code extensions in enterprise environments.

Monitoring Recommendations

Enable endpoint process-creation logging (Windows Event ID 4688 or Sysmon Event ID 1) with full command-line capture on developer workstations.
Baseline normal child-process behavior of Visual Studio Code and alert on deviations, especially interpreter launches immediately after project load.
Monitor DNS and proxy logs for uncommon destinations contacted by developer endpoints during coding activity.

How to Mitigate CVE-2026-47285

Immediate Actions Required

Apply the Microsoft security update referenced in the Microsoft Security Update CVE-2026-47285 advisory to all Visual Studio Code installations.
Instruct developers not to open untrusted repositories, workspaces, or archives received from external sources until the patch is deployed.
Audit installed Visual Studio Code extensions and remove any not required for business use.

Patch Information

Microsoft has published a security update for Visual Studio Code addressing CVE-2026-47285. Consult the Microsoft Security Update CVE-2026-47285 advisory for the fixed version numbers and download locations. Update through the built-in auto-update mechanism or centrally managed software distribution.

Workarounds

Use Visual Studio Code Workspace Trust and open untrusted folders in Restricted Mode until patching is complete.
Isolate review of unknown repositories inside a container, virtual machine, or dev container so command execution cannot reach production credentials.
Remove or restrict shell access from developer accounts that do not require it, limiting the impact of injected commands.

bash

# Configuration example: enforce Workspace Trust in Visual Studio Code settings.json
{
  "security.workspace.trust.enabled": true,
  "security.workspace.trust.startupPrompt": "always",
  "security.workspace.trust.untrustedFiles": "prompt",
  "security.workspace.trust.banner": "always",
  "extensions.autoUpdate": true
}