Code execution through undisclosed local vector
Published Jul 14, 2021 · Updated Aug 10, 2026
Remote code execution in Microsoft Visual Studio Code before 1.58 allows local users to execute code after user interaction. Microsoft has not published the vulnerable component or the operation it performs incorrectly on untrusted input. Exploitation requires local access and user interaction; successful exploitation executes code in the affected user's security context.
Summary
What happened
Remote code execution in Microsoft Visual Studio Code before 1.58 allows local users to execute code after user interaction. Microsoft has not published the vulnerable component or the operation it performs incorrectly on untrusted input. Exploitation requires local access and user interaction; successful exploitation executes code in the affected user's security context.
The record
- CVE
- CVE-2021-34528
- Published
- Jul 14, 2021
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Visual Studio Code
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2021CVE publishedPublication date reported by the CVE source.
- Aug 10, 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.58
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
No sourced classifications are available.
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