Code execution via untrusted workspace interpreter discovery
Published Nov 12, 2024 · Updated Jul 8, 2025
Trust boundary violation in Microsoft's Python extension for Visual Studio Code before 2024.18.2 allows remote attackers to execute code. The getNativePythonFinder path starts Python Environment Tools discovery without checking workspace trust, allowing a repository-supplied Python executable to run. Exploitation requires opening a specially crafted untrusted workspace, after which code executes in the Visual Studio Code user's context.
Summary
What happened
Trust boundary violation in Microsoft's Python extension for Visual Studio Code before 2024.18.2 allows remote attackers to execute code. The getNativePythonFinder path starts Python Environment Tools discovery without checking workspace trust, allowing a repository-supplied Python executable to run. Exploitation requires opening a specially crafted untrusted workspace, after which code executes in the Visual Studio Code user's context.
The record
- CVE
- CVE-2024-49050
- Published
- Nov 12, 2024
- Updated
- Jul 8, 2025
- Vendor
- Microsoft
- Product
- Python extension for Visual Studio Code
- Classifications
- CWE-501, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Jul 8, 2025Record 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 <2024.18.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