Local code execution via uncontrolled Node.js search path
Published Apr 8, 2025 · Updated Aug 10, 2026
Uncontrolled search path handling in Microsoft Visual Studio 2022 allows local users to execute code through its bundled Node.js tooling. Microsoft identifies the Node.js component and search-path class but has not published the affected call, lookup order, or attacker-controlled path. Exploitation requires low local privileges and user interaction; versions 17.8.0 through 17.8.19, 17.10.0 through 17.10.12, and 17.12.0 through 17.12.6 are affected.
Summary
What happened
Uncontrolled search path handling in Microsoft Visual Studio 2022 allows local users to execute code through its bundled Node.js tooling. Microsoft identifies the Node.js component and search-path class but has not published the affected call, lookup order, or attacker-controlled path. Exploitation requires low local privileges and user interaction; versions 17.8.0 through 17.8.19, 17.10.0 through 17.10.12, and 17.12.0 through 17.12.6 are affected.
The record
- CVE
- CVE-2025-29802
- Published
- Apr 8, 2025
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2022 version 17.12
- Classifications
- CWE-427, CAPEC-471, CAPEC-38, T1574.008
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 8, 2025CVE 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=17.12.0 <17.12.7
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