Skip to main content
Mallory
HighVulnerability

CVE-2026-121665: Workspace Trust Bypass in Microsoft Visual Studio Code

Published Nov 10, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 3 in a dayToday
CVSS8.8High · v3.1
EPSS0.44%38th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-121665CWE-501 · Trust Boundary Violation

CVE-2026-121665 is a trust boundary violation in Microsoft Visual Studio Code versions 1.0.0 through versions before 1.145.3. Workspace Trust configuration filtering relies on registered setting schemas, allowing unregistered experiment overrides and dotted child keys beneath restricted settings to evade restrictions. Experiment overrides can indirectly influence restricted settings through experiment-derived defaults, while unregistered child keys can bypass restrictions applied to their registered parent settings. An attacker-controlled workspace can consequently influence restricted behavior even in Restricted Mode. Exploitation involving a crafted workspace and an attacker-controlled notification can permit command execution in the user's context without a workspace trust grant.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation bypasses Workspace Trust protections and can allow commands to execute with the affected user's privileges. An untrusted workspace can influence restricted terminal profiles and experiment treatment values that should be blocked. The CVSS v3.1 assessment assigns high integrity impact and low confidentiality and availability impacts, with a base score of 8.8 and changed scope.

Mitigation

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

Microsoft lists no separate workaround. Until the update is installed, avoid opening untrusted or attacker-supplied workspaces and interacting with attacker-controlled notifications. Restricted Mode alone does not prevent exploitation of this vulnerability.

Remediation

Patch, then assume compromise.

Upgrade Microsoft Visual Studio Code to version 1.145.3 or later. Version 1.145.3, released November 10, 2026, filters unregistered workspace settings while the workspace is untrusted, makes unregistered child settings inherit applicable restrictions from registered ancestors, and updates configuration-change handling during workspace trust transitions.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
FAQ

Frequently asked questions

Is CVE-2026-121665 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-121665 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-121665?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-121665.
Is there a patch for CVE-2026-121665?
Upgrade Microsoft Visual Studio Code to version 1.145.3 or later. Version 1.145.3, released November 10, 2026, filters unregistered workspace settings while the workspace is untrusted, makes unregistered child settings inherit applicable restrictions from registered ancestors, and updates configuration-change handling during workspace trust transitions.
What products are affected by CVE-2026-121665?
Microsoft Corporation Visual Studio Code.
How severe is CVE-2026-121665?
CVE-2026-121665 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.44% (38th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

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

View more in app →
tenable nessus pluginsNews · Nov 16, 2026Security Update for Microsoft Visual Studio Code (November 2026) | Tenable®Referenced in the November 2026 security update for Microsoft Visual Studio Code. Technical details and impact are not provided.Read more ↗zeropath blogNews · Nov 11, 2026Brief Summary: Visual Studio Code CVE-2026-121665 Workspace Trust Bypass via Unregistered and Nested Settings - ZeroPath Blog | ZeroPathA Workspace Trust bypass in Microsoft Visual Studio Code versions 1.0.0 through versions before 1.145.3. Unregistered configuration keys and dotted keys beneath restricted settings could bypass Restricted Mode filtering, allowing attacker-controlled workspaces to influence restricted behavior and potentially execute commands in the user's context. Microsoft's scenario requires opening a crafted workspace and clicking an attacker-controlled notification; the complete exploitation sequence has not been published. The vulnerability has a CVSS 3.1 base score of 8.8 and was fixed in version 1.145.3 on November 10, 2026.Read more ↗msrc microsoftNews · Nov 10, 2026CVE-2026-121665 - Security Update Guide - Microsoft - Visual Studio Code Security Feature Bypass VulnerabilityA trust boundary violation in Visual Studio Code allows an unauthenticated attacker to bypass Workspace Trust protections. Exploitation requires a user to open an attacker-controlled workspace and click an attacker-controlled notification, potentially allowing otherwise-blocked settings to apply and commands to execute with the user's privileges. Microsoft rates the vulnerability Important, with a CVSS v3.1 base score of 8.8, and assesses exploitation as less likely. An official fix is available.Read more ↗cveNews · Nov 10, 2026CVE Record: CVE-2026-121665A trust boundary violation in Microsoft Visual Studio Code permits an unauthenticated network attacker to bypass a security feature with user interaction. The record assigns a high-severity CVSS v3.1 score of 8.8, with changed scope and potentially high integrity impact. Versions from 1.0.0 to before 1.145.3 are affected; the reference identifies a vendor advisory and patch.Read more ↗
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.