Microsoft Visual Studio prior 15.9.79/16.11.55/17.12.19/17.14.30 private personal information

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.2$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Microsoft Visual Studio. This impacts an unknown function. Performing a manipulation results in private personal information. This vulnerability is identified as CVE-2026-32631. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Microsoft Visual Studio. It has been classified as problematic. This affects some unknown processing. The manipulation with an unknown input leads to a private personal information vulnerability. CWE is classifying the issue as CWE-359. The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected. This is going to have an impact on confidentiality.

The weakness was released 04/14/2026 as confirmed security update guide (Website). It is possible to read the advisory at msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2026-32631. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/18/2026). The attack technique deployed by this issue is T1589 according to MITRE ATT&CK.

Upgrading to version 15.9.79, 16.11.55, 17.12.19 or 17.14.30 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1100). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Microsoft .NET Framework
  • Microsoft PowerShell
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • Oracle Linux
  • Microsoft .NET
  • Microsoft Visual Studio 2017
  • Microsoft Visual Studio Code
  • Microsoft Visual Studio 2022
  • Microsoft Visual Studio 2019

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.1
VulDB Meta Temp Score: 5.2

VulDB Base Score: 4.7
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

Vendor Base Score (Microsoft): 7.4
Vendor Vector (Microsoft): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Private personal information
CWE: CWE-359
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Unproven

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒

Upgrade: Visual Studio 15.9.79/16.11.55/17.12.19/17.14.30

Timelineinfo

04/14/2026 VulDB entry created
04/14/2026 +0 days Advisory disclosed
04/14/2026 +0 days Countermeasure disclosed
04/18/2026 +4 days VulDB entry last update

Sourcesinfo

Vendor: microsoft.com

Advisory: msrc.microsoft.com
Status: Confirmed

CVE: CVE-2026-32631 (🔒)
GCVE (CVE): GCVE-0-2026-32631
GCVE (VulDB): GCVE-100-357531
CERT Bund: WID-SEC-2026-1100 - Microsoft DeveloperTools: Mehrere Schwachstellen

Entryinfo

Created: 04/14/2026 20:48
Updated: 04/18/2026 19:51
Changes: 04/14/2026 20:48 (35), 04/14/2026 20:51 (34), 04/18/2026 19:51 (7)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!