dbcve.org
Visual Studio 2019Application · Microsoft

CVE-2025-32702

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 16.11.47 / 17.8.21 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper neutralization of special elements used in a command ('command injection') in Visual Studio allows an unauthorized attacker to execute code locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A command injection vulnerability exists in Visual Studio where improper neutralization of special elements allows an unauthorized attacker to execute code locally. The vulnerability stems from insufficient input sanitization in a code execution path within the IDE.

MitigationApply the vendor-supplied security patch for Visual Studio once available. Until then, restrict local access to trusted users and monitor for suspicious processes spawned from Visual Studio processes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Visual Studio 2019Application
Affected:>= 16.0, < 16.11.47
Visual Studio 2022Application
Affected:>= 17.8.0, < 17.8.21>= 17.10.0, < 17.10.14>= 17.12.0, < 17.12.8>= 17.13.0, < 17.13.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Visual Studio version
    Open Visual Studio, go to Help > About Microsoft Visual Studio, and note the version number displayed. Alternatively, open the Visual Studio Installer, click on the gear icon, and view the version info.
    Affected if The installed version falls within any of these ranges: Visual Studio 2019 version 16.0 through 16.11.46; Visual Studio 2022 versions 17.8.0 through 17.8.20, 17.10.0 through 17.10.13, 17.12.0 through 17.12.7, or 17.13.0 through 17.13.6
  2. Check Visual Studio 2019 exact version via registry
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\SxS\VS7, or check the installed version from Programs and Features > Microsoft Visual Studio 2019 > Uninstall\/Change > Modify.
    Affected if The version shown is 16.0.x through 16.11.46.x (any 16.0 to 16.11.46 release).
  3. Check Visual Studio 2022 exact version via registry
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\SxS\VS7, or view the version in Visual Studio Installer under the installed VS 2022 instance.
    Affected if The version shown is 17.8.x (where x is 0-20), 17.10.x (where x is 0-13), 17.12.x (where x is 0-7), or 17.13.x (where x is 0-6).
  4. Verify command execution features are in use
    Monitor for unusual child processes spawned from any devenv.exe or Visual Studio host processes. Review any custom extensions, external tools, or build event configurations that accept user input and could trigger the vulnerable code path.
    Affected if Untrusted extensions or external tools are enabled, or unexpected child processes appear originating from Visual Studio processes.

You are affected if your installed Visual Studio version matches any of the vulnerable version ranges listed for VS 2019 or VS 2022.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 16.11.47 / 17.8.21 / 17.10.14 or later
Fixed in 16.11.4717.8.2117.10.14
Interim mitigation

Apply the vendor-supplied security patch for Visual Studio once available. Until then, restrict local access to trusted users and monitor for suspicious processes spawned from Visual Studio processes.

Recommended fix High confidence

Visual Studio 2019: upgrade to 16.11.47 or later; Visual Studio 2022: upgrade to 17.13.7 or later

  1. Back up any active projects and settings in Visual Studio
  2. Close all Visual Studio instances
  3. For Visual Studio 2019: Open Visual Studio Installer, locate Visual Studio 2019, and update to version 16.11.47 or later
  4. For Visual Studio 2022: Open Visual Studio Installer, locate Visual Studio 2022, and update to version 17.13.7 (or the latest available version that includes the security fix)
  5. After update completes, launch Visual Studio and verify the update was applied by checking Help > About Microsoft Visual Studio
  6. Restart any running workflows or processes that interact with Visual Studio components
Caveat Standard Visual Studio update - no breaking changes expected; minor update version within same major release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Visual Studio 2019 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32702 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32702 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data