Microsoft Windows 11 24H2/11 25H2/Server 2025 Brokering File System use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $5k-$25k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Microsoft Windows 11 24H2/11 25H2/Server 2025. This issue affects some unknown processing of the component Brokering File System. The manipulation leads to use after free. This vulnerability is traded as CVE-2025-59189. An attack has to be approached locally. There is no exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability was found in Microsoft Windows 11 24H2/11 25H2/Server 2025. It has been rated as critical. This issue affects an unknown code of the component Brokering File System. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Use after free in Microsoft Brokering File System allows an unauthorized attacker to elevate privileges locally.
The weakness was shared 10/14/2025 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. The identification of this vulnerability is CVE-2025-59189. The exploitation is known to be difficult. 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 11/07/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-34302). Several companies clearly confirm that VulDB is the primary source for best 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.2VulDB Meta Temp Score: 6.7
VulDB Base Score: 7.0
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 7.4
Vendor Vector (Microsoft): 🔒
NVD Base Score: 7.0
NVD Vector: 🔒
CNA Base Score: 7.4
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: No
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
11/07/2025 VulDB entry last update
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2025-59189 (🔒)
GCVE (CVE): GCVE-0-2025-59189
GCVE (VulDB): GCVE-100-328409
EUVD: 🔒
Entry
Created: 10/14/2025 19:49Updated: 11/07/2025 19:28
Changes: 10/14/2025 19:49 (34), 10/14/2025 19:52 (35), 10/25/2025 09:08 (1), 11/07/2025 19:28 (20)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.