dbcve.org
Visual Studio 2017Application · Microsoft

CVE-2025-55240

HIGH · 7.3 CVSS v3.1 Developing Published 2025-10-14
Fix available
A fix is available. Upgrade to 15.9.77 / 16.11.52 or later.
See remediation →
73/100
Remediation priority · Elevated

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 access control in Visual Studio allows an authorized attacker to elevate privileges 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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-30.

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 2017Application
Affected:>= 15.0, < 15.9.77
Visual Studio 2019Application
Affected:>= 16.0, < 16.11.52
Visual Studio 2022Application
Affected:>= 17.10.0, < 17.10.20>= 17.12.0, < 17.12.13>= 17.14.0, < 17.14.17

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 15.9.77 / 16.11.52 / 17.10.20 or later
Fixed in 15.9.7716.11.5217.10.20
Recommended fix High confidence

Visual Studio 2017: 15.9.77+ | Visual Studio 2019: 16.11.52+ | Visual Studio 2022: 17.10.20+, 17.12.13+, or 17.14.17+ depending on release channel

  1. Identify the currently installed Visual Studio version by opening Visual Studio and navigating to Help > About Microsoft Visual Studio, or by checking Programs and Features
  2. For Visual Studio 2017 users: Upgrade to version 15.9.77 or later by running Visual Studio Installer and clicking Update
  3. For Visual Studio 2019 users: Upgrade to version 16.11.52 or later by running Visual Studio Installer and clicking Update
  4. For Visual Studio 2022 users: Upgrade to version 17.10.20, 17.12.13, or 17.14.17 (or later) depending on your current release channel by running Visual Studio Installer and clicking Update
  5. Restart Visual Studio after the update completes
  6. Verify the update was successful by checking Help > About Microsoft Visual Studio shows a version >= the fixed version for your product
Caveat Standard Visual Studio minor/patch updates typically have minimal breaking changes; however, ensure any custom extensions are compatible with the new version before updating production environments

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55240 — 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-55240 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