Microsoft Windows 24H2/25H2/26H1/Server 2025 Runtime use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $25k-$100k | 1.35 |
Summary
A vulnerability classified as problematic was found in Microsoft Windows 24H2/25H2/26H1/Server 2025. This vulnerability affects unknown code of the component Runtime. Executing a manipulation can lead to use after free. This vulnerability is registered as CVE-2026-50413. The attack needs to be launched locally. No exploit is available.
Details
A vulnerability was found in Microsoft Windows 24H2/25H2/26H1/Server 2025. It has been declared as problematic. This vulnerability affects an unknown function of the component Runtime. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Use after free in Windows Runtime allows an authorized attacker to elevate privileges locally.
The advisory is shared for download at msrc.microsoft.com. This vulnerability was named CVE-2026-50413 since 06/04/2026. The exploitation appears to be easy. The attack needs to be approached locally. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $25k-$100k (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.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/04/2026 CVE reserved07/14/2026 Advisory disclosed
07/14/2026 VulDB entry created
07/14/2026 VulDB entry last update
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-50413 (🔒)
GCVE (CVE): GCVE-0-2026-50413
GCVE (VulDB): GCVE-100-378700
Entry
Created: 07/14/2026 23:02Changes: 07/14/2026 23:02 (53)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.