Code execution via unsafe notebook rendering
Published Dec 29, 2023 · Updated Aug 19, 2026
Remote code execution in Microsoft's Python extension for Visual Studio Code before 2020.9.2 allows attackers to run code via a crafted file. The notebook renderer processes attacker-controlled content without adequate safeguards, permitting code execution in the editor context. Exploitation requires a user to open the crafted file in Visual Studio Code with the extension installed.
Summary
What happened
Remote code execution in Microsoft's Python extension for Visual Studio Code before 2020.9.2 allows attackers to run code via a crafted file. The notebook renderer processes attacker-controlled content without adequate safeguards, permitting code execution in the editor context. Exploitation requires a user to open the crafted file in Visual Studio Code with the extension installed.
The record
- CVE
- CVE-2020-17163
- Published
- Dec 29, 2023
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Python extension for Visual Studio Code
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 29, 2023CVE 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=2020 <publication
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.
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