CVE-2025-32702 json
Visual Studio Remote Code Execution Vulnerability
published last yr. modified 4mo ago also EUVD-2025-14410
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
Improper neutralization of special elements used in a command ('command injection') in Visual Studio allows an unauthorized attacker to execute code locally.
Patch / fix
- Microsoft Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) 16.11.47
- Microsoft Microsoft Visual Studio 2022 version 17.10 17.10.14
- Microsoft Microsoft Visual Studio 2022 version 17.12 17.12.8
- Microsoft Microsoft Visual Studio 2022 version 17.13 17.13.7
- Microsoft Microsoft Visual Studio 2022 version 17.8 17.8.21
Is CVE-2025-32702 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Microsoft Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)
- Microsoft Microsoft Visual Studio 2022 version 17.10
- Microsoft Microsoft Visual Studio 2022 version 17.12
- Microsoft Microsoft Visual Studio 2022 version 17.13
- Microsoft Microsoft Visual Studio 2022 version 17.8
Classification
- Weakness
-
- CWE-77 Improper Neutralization of Special Elements used in a Command
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2025-32702
vendor-advisory, patch
Sources
- CVE List CVE-2025-32702
- NVD CVE-2025-32702
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.