Microsoft Windows up to Server 2025 Inbox COM Objects use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $5k-$25k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Microsoft Windows up to Server 2025. Affected by this issue is some unknown functionality of the component Inbox COM Objects. Performing a manipulation results in use after free. This vulnerability is known as CVE-2025-58731. Attacking locally is a requirement. No exploit is available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability, which was classified as critical, was found in Microsoft Windows up to Server 2025. This affects an unknown code of the component Inbox COM Objects. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Use after free in Inbox COM Objects allows an unauthorized attacker to execute code locally.
The weakness was published 10/14/2025 as confirmed security update guide (Website). It is possible to read the advisory at msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2025-58731. The exploitability is told to be difficult. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 10/17/2025).
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-34312). Statistical analysis made it clear that VulDB provides the best quality 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: 7.0VulDB Meta Temp Score: 6.4
VulDB Base Score: 7.0
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 7.0
Vendor Vector (Microsoft): 🔒
CNA Base Score: 7.0
CNA Vector (Microsoft): 🔒
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: Partially
Availability: 🔒
Status: Unproven
EPSS Score: 🔒
EPSS Percentile: 🔒
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: PatchStatus: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Timeline
10/14/2025 VulDB entry created10/14/2025 Advisory disclosed
10/14/2025 Countermeasure disclosed
10/17/2025 VulDB entry last update
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2025-58731 (🔒)
GCVE (CVE): GCVE-0-2025-58731
GCVE (VulDB): GCVE-100-328395
EUVD: 🔒
Entry
Created: 10/14/2025 19:41Updated: 10/17/2025 08:51
Changes: 10/14/2025 19:41 (33), 10/14/2025 19:45 (36), 10/16/2025 22:12 (11), 10/17/2025 08:51 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.