CVE-2025-49693 is a local privilege escalation vulnerability in the Microsoft Brokering File System, a Windows kernel-mode component involved in file operations and inter-process communication. The flaw is caused by a double free condition in memory management, where the same memory region can be released more than once due to improper handling of allocation and deallocation logic. An authenticated local attacker can trigger the vulnerable code path with crafted input, causing kernel memory corruption. In successful exploitation scenarios, the corrupted kernel state can be used to overwrite sensitive kernel structures, including security-relevant process token data, enabling escalation from a low-privileged context to SYSTEM.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.