Skip to content
Noroxi
NVD / CVE Program· CNA microsoft

CVE-2025-32703: Visual Studio Information Disclosure Vulnerability

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.50% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) 15.9.73; Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) 16.11.47; Microsoft Visual Studio 2022 version 17.10 17.10.14.

Low priority for now. Upgrade to Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) 15.9.73; Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) 16.11.47; Microsoft Visual Studio 2022 version 17.10 17.10.14 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 13, 2025
Updated
Jun 17, 2026
EPSS
0.5% · 42th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · microsoft
5.5
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-32703

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for microsoft records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
microsoftvisual studio 2017
microsoftvisual studio 2019
microsoftvisual studio 2022

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • microsoft visual studio 201715.0 and later · before 15.9.73
  • microsoft visual studio 201916.0 and later · before 16.11.47
  • microsoft visual studio 202217.8.0 and later · before 17.8.21
  • microsoft visual studio 202217.10.0 and later · before 17.10.14
  • microsoft visual studio 202217.12.0 and later · before 17.12.8
  • microsoft visual studio 202217.13.0 and later · before 17.13.7

Versions reported by the vendor

Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.

  • Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)

    • 15.9.0 and later · before 15.9.73affected

  • Microsoft Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)

    • 16.11.0 and later · before 16.11.47affected

  • Microsoft Microsoft Visual Studio 2022 version 17.10

    • 17.10.0 and later · before 17.10.14affected

  • Microsoft Microsoft Visual Studio 2022 version 17.12

    • 17.12.0 and later · before 17.12.8affected

  • Microsoft Microsoft Visual Studio 2022 version 17.13

    • 17.13.0 and later · before 17.13.7affected

  • Microsoft Microsoft Visual Studio 2022 version 17.8

    • 17.8.0 and later · before 17.8.21affected

Same product

microsoft: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-36952Visual Studio Remote Code Execution Vulnerability
    46Plan
  • CVE-2019-1349A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code E
    45Plan
  • CVE-2019-1350A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code E
    43Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-21206Feb 11, 2025 · Visual Studio Installer Elevation of Privilege Vulnerability
    29Monitor
  • ← EarlierCVE-2025-24998Mar 11, 2025 · Visual Studio Elevation of Privilege Vulnerability
    29Monitor
  • Later →CVE-2025-55240Oct 14, 2025 · Visual Studio Elevation of Privilege Vulnerability
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)15.9.73 · Release NotesMicrosoft (MSRC)
Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)16.11.47 · Release NotesMicrosoft (MSRC)
Microsoft Visual Studio 2022 version 17.1017.10.14 · Release NotesMicrosoft (MSRC)
Microsoft Visual Studio 2022 version 17.1217.12.8 · Release NotesMicrosoft (MSRC)
Microsoft Visual Studio 2022 version 17.1317.13.7 · Release NotesMicrosoft (MSRC)
Microsoft Visual Studio 2022 version 17.817.8.21 · Release NotesMicrosoft (MSRC)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

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

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records