CVE Tools
Track your stack

CVE-2025-32703

Visual Studio Information Disclosure Vulnerability

No known exploitation. EPSS puts it in the 43rd percentile. Fixed versions are out.

CVSS 3.15.5MediumEPSS percentile43rd0.5% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix5 products5 fixed builds listed below
Check it yourself

OpenVAS · 3 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.836218

Run the check

Published Updated Sources: CVE.org, NVD, BDU

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Microsoft Visual Studio 2017 version 15.9Affected: ≥ 15.9.0, < 15.9.73Upgrade to: 15.9.73Stated by: CVE record
  • Microsoft Visual Studio 2019 version 16.11Affected: ≥ 16.11.0, < 16.11.47Upgrade to: 16.11.47Stated by: CVE record
  • Microsoft Visual Studio 2022 version 17.10Affected: ≥ 17.10.0, < 17.10.14Upgrade to: 17.10.14Stated by: CVE record
  • Microsoft Visual Studio 2022 version 17.12Affected: ≥ 17.12.0, < 17.12.8Upgrade to: 17.12.8Stated by: CVE record
  • Microsoft Visual Studio 2022 version 17.13Affected: ≥ 17.13.0, < 17.13.7Upgrade to: 17.13.7Stated by: CVE record

Versions as the sources state them. 4 more products have version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Insufficient granularity of access control in Visual Studio allows an authorized attacker to disclose information locally.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS43rd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 43rd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 408 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Publishedweakness classified, att&ck mapped

Affected products

And 4 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 5.5 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Visual Studio 2017, not every advisory.