Skip to main content
Mallory
← Back to News
endpoint-software-vulnerabilitywidely-deployed-product-advisory

Visual Studio Code Workspace Trust Bypass Can Enable Commands Without Trust Approval

Vulnerability Disclosure · 5 sources · Updated 6d ago · First seen Nov 11, 2026

Visual Studio Code Workspace Trust Bypass Can Enable Commands Without Trust Approval

Microsoft patched CVE-2026-121665, a Visual Studio Code Workspace Trust bypass affecting versions 1.0.0 through releases before 1.145.3. An attacker must persuade a user to open a crafted workspace and click an attacker-controlled notification; successful exploitation can allow commands to execute in the user’s context without granting workspace trust. ZeroPath describes configuration-filtering gaps involving unregistered experiment overrides and dotted keys beneath restricted settings, allowing untrusted workspace settings to influence restricted behavior. The flaw is classified as a trust boundary violation, CWE-501. Microsoft rates it Important, with a CVSS v3.1 score of 8.8, and released the fix on November 10. (Microsoft advisory, ZeroPath analysis)

Microsoft also disclosed CVE-2026-121662, a separate command-injection vulnerability that can bypass Workspace Trust when a user opens a specially crafted workspace, enabling code execution in the user’s context. It carries an Important rating and a CVSS v3.1 score of 8.6. At initial publication, Microsoft reported neither public disclosure nor observed exploitation for either flaw, but assessed exploitation as more likely for CVE-2026-121662 and less likely for CVE-2026-121665. Organizations should upgrade affected VS Code installations to 1.145.3 or later for CVE-2026-121665 and verify deployment of Microsoft’s official fix for CVE-2026-121662; Workspace Trust alone does not mitigate these attack paths. (Microsoft RCE advisory)

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Nov 10, 2026
  1. Reported Nov 11, 20267d ago

    ZeroPath details and verifies the CVE-2026-121665 filtering bypass

    ZeroPath documented how unregistered experiment overrides and dotted keys beneath restricted settings bypassed Workspace Trust filtering. Live Code OSS verification showed that an unfixed build accepted these settings in Restricted Mode while the fixed build rejected them; the analysis did not establish a complete command-execution chain.

    Brief Summary: Visual Studio Code CVE-2026-121665 Workspace Trust Bypass via Unregistered and Nested Settings - ZeroPath Blog | ZeroPath
  2. Reported Nov 10, 20268d ago

    Microsoft discloses a separate Workspace Trust command-injection vulnerability

    Microsoft disclosed CVE-2026-121662, an 8.6-CVSS command-injection vulnerability that can execute code in the user's context when a crafted workspace is opened, without requiring workspace trust. Microsoft indicated an official fix was available, reported no observed exploitation, and assessed exploitation as more likely.

    CVE-2026-121662 - Security Update Guide - Microsoft - Visual Studio Code Remote Code Execution Vulnerability
  3. Nov 10, 20268d ago

    Microsoft releases Visual Studio Code 1.145.3 to fix the trust bypass

    Microsoft released Visual Studio Code 1.145.3 as the official fix for CVE-2026-121665. The patch blocks unregistered workspace settings in untrusted workspaces and makes unregistered dotted settings inherit restrictions from registered parent settings.

    Brief Summary: Visual Studio Code CVE-2026-121665 Workspace Trust Bypass via Unregistered and Nested Settings - ZeroPath Blog | ZeroPath
  4. Nov 10, 20268d ago

    Microsoft discloses CVE-2026-121665 Workspace Trust bypass

    Microsoft published CVE-2026-121665, a trust boundary violation affecting Visual Studio Code versions 1.0.0 through versions before 1.145.3, with a CVSS score of 8.8. Exploitation requires opening a crafted workspace and clicking an attacker-controlled notification, potentially allowing commands to run without granting workspace trust; Microsoft reported no observed exploitation at disclosure.

    CVE Record: CVE-2026-121665
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.