Visual Studio Information Disclosure Vulnerability

published 2025-05-13 17 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-14442

cvss: 5.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits: 0; none known

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

Patch / fix

fixed in 6 links 1

Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) 15.9.73
Microsoft Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) 16.11.47
Microsoft Microsoft Visual Studio 2022 version 17.10 17.10.14
Microsoft Microsoft Visual Studio 2022 version 17.12 17.12.8
Microsoft Microsoft Visual Studio 2022 version 17.13 17.13.7
Microsoft Microsoft Visual Studio 2022 version 17.8 17.8.21

msrc.microsoft.com/update-guide/vulnerability/CVE-2025-32703 advisory

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 17 mo ago (2025-05-13)

Exploit prediction

0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
CNA	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected products

Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)
Microsoft Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)
Microsoft Microsoft Visual Studio 2022 version 17.10
Microsoft Microsoft Visual Studio 2022 version 17.12
Microsoft Microsoft Visual Studio 2022 version 17.13
Microsoft Microsoft Visual Studio 2022 version 17.8

Classification

Weakness

CWE-1220 Insufficient Granularity of Access Control
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

msrc.microsoft.com /update-guide/vulnerability/CVE-2025-32703
vendor-advisory, patch

Sources

CVE List CVE-2025-32703
NVD CVE-2025-32703

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary