Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2025-32701: Windows Common Log File System Driver Use-After-Free Privilege Escalation

Published May 13, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS1.4%73rd percentile
CISA KEVYesAdded May 13, 2025
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2025-32701CWE-416 · Use After Free

CVE-2025-32701 is a local elevation-of-privilege vulnerability in the Windows Common Log File System (CLFS) driver. The flaw is a use-after-free condition in kernel-mode CLFS object handling that can occur when the driver improperly manages memory references after freeing an internal log-related object. A local, authorized attacker can trigger the vulnerable state through crafted interaction with CLFS log operations and then reclaim the freed memory with controlled data, causing the kernel to dereference a stale pointer. Successful exploitation results in execution in kernel context and elevation to SYSTEM. Microsoft reported exploitation in the wild at the time of disclosure, and the vulnerability has been associated with post-compromise activity where attackers use it as a privilege-escalation primitive after obtaining initial access.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker who already has local code execution or an authenticated foothold on the target system to escalate privileges to SYSTEM. Because the flaw is in a kernel driver, exploitation can enable arbitrary code execution in kernel context, full takeover of the affected host, disabling or tampering with security controls, credential theft, persistence, lateral movement preparation, and follow-on ransomware or espionage activity. The vulnerability is particularly valuable as a post-exploitation primitive for converting limited user-level access into complete control of the system.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce opportunities for local code execution and post-compromise privilege escalation by enforcing least privilege, restricting interactive logon, limiting execution of untrusted code, and hardening application control policies. Increase monitoring for anomalous CLFS-related activity and suspicious kernel-level exploitation behavior, including unusual interactions with the CLFS driver and unexpected use of CLFS APIs from low-privilege processes. Behavioral detections, endpoint protection, attack surface reduction controls, and rapid containment of initial-access malware can reduce the likelihood that attackers can leverage the flaw as part of an intrusion chain. These measures are compensating controls only and do not remove the underlying vulnerability.

Remediation

Patch, then assume compromise.

Apply Microsoft's May 2025 security updates for affected Windows versions. The available information indicates the issue was addressed in Microsoft's May 2025 Patch Tuesday release, including updates referenced as KB5058405 and KB5058379 for affected platforms. Organizations should prioritize patching internet-connected endpoints, high-value workstations, terminal servers, and systems where untrusted users can obtain local execution. Standard patch validation and expedited deployment are warranted because Microsoft confirmed active exploitation in the wild.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
FAQ

Frequently asked questions

Is CVE-2025-32701 exploited in the wild?
Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on May 13, 2025.
Is there a public exploit for CVE-2025-32701?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-32701.
Is there a patch for CVE-2025-32701?
Apply Microsoft's May 2025 security updates for affected Windows versions. The available information indicates the issue was addressed in Microsoft's May 2025 Patch Tuesday release, including updates referenced as KB5058405 and KB5058379 for affected platforms.
What products are affected by CVE-2025-32701?
Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, and 14 more.
How severe is CVE-2025-32701?
CVE-2025-32701 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 1.4% (73rd percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity8Community discussion across Reddit, Mastodon, and other social sources.