Skip to main content
Mallory
HighVulnerability

CVE-2026-102236: Visual Studio Code Workspace Trust Bypass

Published Nov 10, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days5 mentions · peak 3 in a dayToday
CVSS8.6High · v3.1
EPSS0.43%37th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-102236CWE-1021 · Improper Restriction of Rendered…

CVE-2026-102236 is a security feature bypass vulnerability in Visual Studio Code caused by improper restriction of rendered UI layers or frames. An attacker can convince a user to open a specially crafted workspace and bypass Workspace Trust, allowing attacker-controlled content to execute commands or code in the user's context without the user first granting trust.

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 defeats the Workspace Trust security boundary and permits command or code execution in the affected user's context. This can compromise data accessible to that user, allow unauthorized modifications, and disrupt availability. The vulnerability is rated Important, with a CVSS v3.1 base score of 8.6 and high confidentiality, integrity, and availability impacts.

Mitigation

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

Until the update is installed, avoid opening workspaces from untrusted or unverified sources. Workspace Trust alone should not be relied upon to contain malicious workspace content on affected installations. No vendor-specific interim workaround is identified in the available information.

Remediation

Patch, then assume compromise.

Install the applicable Microsoft security update for Visual Studio Code. An official vendor fix is available, but the affected version ranges and specific fixed release are not identified in the available information.

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-102236 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-102236 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-102236?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-102236.
Is there a patch for CVE-2026-102236?
Install the applicable Microsoft security update for Visual Studio Code. An official vendor fix is available, but the affected version ranges and specific fixed release are not identified in the available information.
What products are affected by CVE-2026-102236?
Microsoft Corporation Visual Studio Code.
How severe is CVE-2026-102236?
CVE-2026-102236 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 0.43% (37th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

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

View more in app →
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.