CVE-2026-50361
Analyzed Analyzed - Analysis Complete

Microsoft Brokering File System Double Free Local Privilege Escalation

Vulnerability report for CVE-2026-50361, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-14

Last updated on: 2026-07-22

Assigner: Microsoft Corporation

Description

Double free in Microsoft Brokering File System allows an authorized attacker to elevate privileges locally.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-14
Last Modified
2026-07-22
Generated
2026-08-04
AI Q&A
2026-07-15
EPSS Evaluated
2026-08-02
NVD
EUVD

Affected Vendors & Products

Showing 7 associated CPEs
Vendor Product Version / Range
microsoft windows_11_26h1 to 10.0.28000.2269 (exc)
microsoft windows_server_2025 to 10.0.26100.33158 (exc)
microsoft windows_11_26h1 to 10.0.28000.2525 (exc)
microsoft windows_11_24h2 to 10.0.26100.8875 (exc)
microsoft windows_11_24h2 to 10.0.26100.8875 (exc)
microsoft windows_11_25h2 to 10.0.26200.8875 (exc)
microsoft windows_11_25h2 to 10.0.26200.8875 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-415 The product calls free() twice on the same memory address.
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-50361 is a vulnerability in the Microsoft Brokering File System. It involves a 'double free' error, which occurs when a program incorrectly frees the same memory location twice. This can lead to memory corruption and unpredictable behavior in the system.

An authorized attacker with local access to the system can exploit this vulnerability to elevate their privileges. This means they could gain higher-level permissions than they are supposed to have, potentially allowing them to perform actions like installing software, accessing restricted data, or modifying system configurations.

Detection Guidance

The provided context does not include specific detection methods or commands for identifying the presence of CVE-2026-50361 on a network or system. Detection typically involves checking for vulnerable versions of the Microsoft Brokering File System or using security tools that can identify memory corruption issues like double free vulnerabilities.

For accurate detection guidance, refer to Microsoft's official documentation or security advisories, which may provide updated tools or scripts to scan for this vulnerability.

Impact Analysis

If you are using a system with the Microsoft Brokering File System, this vulnerability could allow an attacker with local access to elevate their privileges on your system.

  • An attacker could gain administrative or higher-level access, allowing them to take control of your system.
  • They could install malicious software, steal sensitive data, or modify system settings without your knowledge.
  • The vulnerability could be used to bypass security measures, leading to further exploitation of your system or network.

Since the attacker needs local access, the risk is higher in environments where multiple users share a system or where physical access to machines is not tightly controlled.

Compliance Impact

This vulnerability could impact compliance with several common standards and regulations, depending on the context of its exploitation.

  • GDPR (General Data Protection Regulation): If the vulnerability is exploited to access or exfiltrate personal data of EU citizens, it could lead to a data breach. Organizations are required to protect personal data under GDPR, and failure to do so could result in significant fines and legal consequences.
  • HIPAA (Health Insurance Portability and Accountability Act): In healthcare environments, if the vulnerability is used to access protected health information (PHI), it could constitute a breach under HIPAA. Covered entities must ensure the confidentiality, integrity, and availability of PHI, and a breach could lead to penalties.
  • Other standards like ISO 27001, NIST, or PCI DSS may also be affected if the vulnerability leads to unauthorized access or control over systems handling sensitive information. Compliance with these standards often requires maintaining strong access controls and protecting against privilege escalation attacks.

Organizations should assess the risk posed by this vulnerability and take appropriate measures to mitigate it to avoid potential compliance violations.

Mitigation Strategies

Based on the provided context, the following immediate steps are recommended to mitigate CVE-2026-50361:

  • Apply the latest security updates or patches provided by Microsoft for the Microsoft Brokering File System. Refer to the official Microsoft update guide for this CVE.
  • Restrict local access to systems running the vulnerable component to minimize the risk of exploitation by an authorized attacker.
  • Monitor Microsoft's security advisories for additional guidance or workarounds if a patch is not immediately available.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-50361. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart