Microsoft Windows up to Server 2025 Notification type conversion

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.
3.3$5k-$25k0.67

Summaryinfo

A vulnerability was found in Microsoft Windows. It has been classified as problematic. This affects an unknown part of the component Notification. The manipulation leads to type conversion. This vulnerability is uniquely identified as CVE-2026-50337. Local access is required to approach this attack. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Microsoft Windows. This issue affects an unknown code block of the component Notification. The manipulation with an unknown input leads to a type conversion vulnerability. Using CWE to declare the problem leads to CWE-704. The product does not correctly convert an object, resource, or structure from one type to a different type. Impacted is integrity. The summary by CVE is:

Incorrect type conversion or cast in Windows Notification allows an authorized attacker to elevate privileges locally.

The advisory is shared at msrc.microsoft.com. The identification of this vulnerability is CVE-2026-50337 since 06/04/2026. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 07/14/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.3

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

CVSSv2info

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

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

Exploitinginfo

Class: Type conversion
CWE: CWE-704
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

06/04/2026 CVE reserved
07/14/2026 +40 days Advisory disclosed
07/14/2026 +0 days VulDB entry created
07/14/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: microsoft.com
Product: microsoft.com

Advisory: msrc.microsoft.com
Status: Confirmed

CVE: CVE-2026-50337 (🔒)
GCVE (CVE): GCVE-0-2026-50337
GCVE (VulDB): GCVE-100-378677
scip Labs: https://www.scip.ch/en/?labs.20161215

Entryinfo

Created: 07/14/2026 22:51
Changes: 07/14/2026 22:51 (53)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!