Microsoft Visual Studio 2019 version 16.11…: Improper Neutralization of Special Elements used in a Command
CVE-2025-32702 is a high-severity improper neutralization of special elements used in a command vulnerability in Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) from Microsoft, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 16.11.47 as the first without the flaw, so updating Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.62% chance of exploitation within 30 days, higher than 50% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) to 16.11.47 or a later version.
- Update Microsoft Visual Studio 2022 version 17.10 to 17.10.14 or a later version.
- Update Microsoft Visual Studio 2022 version 17.12 to 17.12.8 or a later version.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) | 16.11.0 up to, but not including, 16.11.47 | 16.11.47 |
| Microsoft | Microsoft Visual Studio 2022 version 17.10 | 17.10.0 up to, but not including, 17.10.14 | 17.10.14 |
| Microsoft | Microsoft Visual Studio 2022 version 17.12 | 17.12.0 up to, but not including, 17.12.8 | 17.12.8 |
| Microsoft | Microsoft Visual Studio 2022 version 17.13 | 17.13.0 up to, but not including, 17.13.7 | 17.13.7 |
| Microsoft | Microsoft Visual Studio 2022 version 17.8 | 17.8.0 up to, but not including, 17.8.21 | 17.8.21 |
| Microsoft | Visual Studio 2019 | 16.0 up to, but not including, 16.11.47 | 16.11.47 |
| Microsoft | Visual Studio 2022 | 17.8.0 up to, but not including, 17.8.21; 17.10.0 up to, but not including, 17.10.14; 17.12.0 up to, but not including, 17.12.8; 17.13.0 up to, but not including, 17.13.7 | 17.8.21, 17.10.14, 17.12.8, 17.13.7 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).
Official description
Improper neutralization of special elements used in a command ('command injection') in Visual Studio allows an unauthorized attacker to execute code locally.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in a Command
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
How developers prevent this class of flaw
- If at all possible, use library calls rather than external processes to recreate the desired functionality.
- If possible, ensure that all external commands called from the program are statically created.
- Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
More Improper Neutralization of Special Elements used in a Command vulnerabilities (CWE-77)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Recent Improper Neutralization of Special Elements used in a Command vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.7 High severity
Spotted an error? Tell us.