Microsoft Visual Studio 2022 version 17.10: Improper Neutralization of Special Elements used in a Command
CVE-2025-47959 is a high-severity improper neutralization of special elements used in a command vulnerability in Microsoft Visual Studio 2022 version 17.10 from Microsoft, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. The record lists version 17.10.16 as the first without the flaw, so updating Microsoft Visual Studio 2022 version 17.10 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 11.4% chance of exploitation within 30 days, which is in the top 3.93% of all scored CVEs.
EPSS places it among the vulnerabilities most likely to be exploited soon.
What to do
- Update Microsoft Visual Studio 2022 version 17.10 to 17.10.16 or a later version.
- Update Microsoft Visual Studio 2022 version 17.12 to 17.12.9 or a later version.
- Update Microsoft Visual Studio 2022 version 17.14 to 17.14.5 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 2022 version 17.10 | 17.10.0 up to, but not including, 17.10.16 | 17.10.16 |
| Microsoft | Microsoft Visual Studio 2022 version 17.12 | 17.12.0 up to, but not including, 17.12.9 | 17.12.9 |
| Microsoft | Microsoft Visual Studio 2022 version 17.14 | 17.14.0 up to, but not including, 17.14.5 | 17.14.5 |
| Microsoft | Microsoft Visual Studio 2022 version 17.8 | 17.8.0 up to, but not including, 17.8.22 | 17.8.22 |
| Microsoft | Visual Studio 2022 | 17.8.0 up to, but not including, 17.8.22; 17.10.0 up to, but not including, 17.10.16; 17.12.0 up to, but not including, 17.12.9; 17.14.0 up to, but not including, 17.14.5 | 17.8.22, 17.10.16, 17.12.9, 17.14.5 |
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
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- 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:N/AC:H/PR:L/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 authorized attacker to execute code over a network.
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
Other vulnerabilities in Microsoft Visual Studio 2022 version 17.10
- 9.9 Critical severity
- 8.0 High severity
- 7.8 High severity
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
- 7.2 High severity
Spotted an error? Tell us.