Workspace Trust bypass via nested settings
Published Sep 8, 2026 · Updated Sep 9, 2026
Workspace Trust bypass in Microsoft Visual Studio Code before 1.136.2 allows local users to apply restricted workspace settings. The Workspace Trust filter checks each raw top-level JSON key against the configuration registry, but it does not resolve nested objects to their equivalent dotted setting paths. Exploitation requires a user to open an attacker-crafted workspace in Restricted Mode; the applied settings can execute commands or code with the user's permissions.
Summary
What happened
Workspace Trust bypass in Microsoft Visual Studio Code before 1.136.2 allows local users to apply restricted workspace settings. The Workspace Trust filter checks each raw top-level JSON key against the configuration registry, but it does not resolve nested objects to their equivalent dotted setting paths. Exploitation requires a user to open an attacker-crafted workspace in Restricted Mode; the applied settings can execute commands or code with the user's permissions.
The record
- CVE
- CVE-2026-70334
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- Vendor
- Microsoft
- Product
- Visual Studio Code
- Classifications
- CWE-184, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <1.136.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo