User-assisted code execution via notebook workspace settings
Published May 21, 2020 · Updated Aug 19, 2026
Code execution in the Microsoft Python extension before 2020.5.0 allows attackers to run code by opening a crafted notebook in Visual Studio Code. The notebook workspace-settings loader accepts attacker-controlled execution settings without the user-level enforcement applied by the update, causing extension tooling to launch code as the current user. Exploitation requires the Python extension and user interaction with the file; resulting code can read, change, or delete data accessible to that user.
Summary
What happened
Code execution in the Microsoft Python extension before 2020.5.0 allows attackers to run code by opening a crafted notebook in Visual Studio Code. The notebook workspace-settings loader accepts attacker-controlled execution settings without the user-level enforcement applied by the update, causing extension tooling to launch code as the current user. Exploitation requires the Python extension and user interaction with the file; resulting code can read, change, or delete data accessible to that user.
The record
- CVE
- CVE-2020-1192
- Published
- May 21, 2020
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Visual Studio Code
- Classifications
- T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 19, 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 <publication
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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