Skip to content
Server Security Center
KEVhigh7.8

CVE-2025-32701: Microsoft Windows Common Log File System (CLFS) Driver Use-After-Free

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-05-13.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
1.4%
higher than 73.4% of all CVEs
Added to CISA KEV
2025-05-13
US federal due date 2025-06-03
Automatable (CISA SSVC)
no
technical impact: total

CVE-2025-32701 explained

CVE-2025-32701 is a use-after-free flaw in the Windows Common Log File System (CLFS) Driver in Microsoft Windows. An authorized local attacker can use it to elevate privileges. CISA lists it as known to be exploited, so affected systems should be patched promptly.

Impact

An attacker who already has low-privileged local access can elevate privileges without any user interaction. Successful exploitation has high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning total control of the affected component. CISA rates it as not automatable, so exploitation is not expected at scale without manual steps. The flaw is not reachable over the network on its own. Attackers are known to use this vulnerability.

Who is affected

The CVE record lists Windows 10 Versions 1507, 1607, 1809, 21H2 and 22H2, Windows 11 versions 22H2, 22H3, 23H2 and 24H2, Windows Server 2008 R2 Service Pack 1 (including Server Core), and Windows Server 2008 Service Pack 2. Fixed builds include 10.0.10240.21014, 10.0.14393.8066, 10.0.17763.7314, 10.0.19044.5854, 10.0.19045.5854, 10.0.22621.5335, 10.0.22631.5335, 10.0.26100.4061, 6.1.7601.27729 and 6.0.6003.23279. The page lists 13 further products.

Written with AI from the data on this page and checked against it automatically.

Official description

Use after free in Windows Common Log File System Driver allows an authorized attacker to elevate privileges locally.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.21014
    Fixed in
    • 10.0.10240.21014
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.8066
    Fixed in
    • 10.0.14393.8066
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.7314
    Fixed in
    • 10.0.17763.7314
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.5854
    Fixed in
    • 10.0.19044.5854
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.5854
    Fixed in
    • 10.0.19045.5854
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.5335
    Fixed in
    • 10.0.22621.5335
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.5335
    Fixed in
    • 10.0.22631.5335
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.5335
    Fixed in
    • 10.0.22631.5335
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.4061
    Fixed in
    • 10.0.26100.4061
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27729
    Fixed in
    • 6.1.7601.27729
Show 15 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27729
    Fixed in
    • 6.1.7601.27729
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.23279
    Fixed in
    • 6.0.6003.23279
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.23279
    Fixed in
    • 6.0.6003.23279
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25475
    Fixed in
    • 6.2.9200.25475
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25475
    Fixed in
    • 6.2.9200.25475
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22577
    Fixed in
    • 6.3.9600.22577
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22577
    Fixed in
    • 6.3.9600.22577
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.8066
    Fixed in
    • 10.0.14393.8066
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.8066
    Fixed in
    • 10.0.14393.8066
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.7314
    Fixed in
    • 10.0.17763.7314
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.7314
    Fixed in
    • 10.0.17763.7314
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.3692
    Fixed in
    • 10.0.20348.3692
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1611
    Fixed in
    • 10.0.25398.1611
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.4061
    Fixed in
    • 10.0.26100.4061
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.4061
    Fixed in
    • 10.0.26100.4061

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.21014
    • Microsoft Windows 10 Version 1607: 10.0.14393.8066
    • Microsoft Windows 10 Version 1809: 10.0.17763.7314
    • Microsoft Windows 10 Version 21H2: 10.0.19044.5854
    • Microsoft Windows 10 Version 22H2: 10.0.19045.5854
    • Microsoft Windows 11 version 22H2: 10.0.22621.5335
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-32701
  • CISA's deadline for US federal agencies: 2025-06-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to the fixed build listed for its Windows version.
  2. Prioritize systems where many users have local or remote interactive access, such as shared workstations and terminal servers.
  3. Follow the Microsoft advisory and CISA's required action; discontinue use of the product where mitigations are unavailable.
  4. Limit local logon rights and remove unnecessary low-privileged accounts to reduce who can attempt local privilege elevation.
  5. Check systems for signs of compromise, such as unexpected privileged accounts or processes, since the flaw is known to be exploited.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-416 Use After Free

Questions about CVE-2025-32701

Can this vulnerability be exploited remotely?
Not directly. The attack vector is local and the attacker needs low-privileged access to the system first. Exploitation then requires no user interaction.
Is CVE-2025-32701 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-05-13, with a US federal due date of 2025-06-03. Whether it is used in ransomware campaigns is unknown.
Which update fixes the issue?
The CVE record names a fixed build per Windows version, for example 10.0.26100.4061 for Windows 11 Version 24H2 and 10.0.19045.5854 for Windows 10 Version 22H2. Install the Microsoft security update that reaches or exceeds the listed build.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.