Skip to content
Server Security Center
KEVhigh7.8

CVE-2025-32706: Microsoft Windows Common Log File System (CLFS) Driver Heap-Based Buffer Overflow

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)
2.3%
higher than 83.9% 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-32706 explained

CVE-2025-32706 is an improper input validation flaw in the Windows Common Log File System (CLFS) driver in Microsoft Windows. It lets an authorized local attacker elevate privileges. CISA lists it as known to be exploited, so affected systems should be patched with priority.

Impact

An attacker who already has low-privileged local access can elevate privileges without user interaction. Successful exploitation gives high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so attackers cannot exploit it at scale without manual steps. Separately, the local attack vector means the attacker needs access to the system itself. 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; and Windows Server 2008 R2 SP1 (including Server Core) and Server 2008 SP2. Example fixed builds: 10.0.19045.5854 (Windows 10 22H2), 10.0.22631.5335 (Windows 11 23H2), 10.0.26100.4061 (Windows 11 24H2), 6.1.7601.27729 (Server 2008 R2 SP1). Builds below the listed fixed version are affected. Further products are listed on this page.

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

Official description

Improper input validation 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-32706
  • 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, for example 10.0.26100.4061 for Windows 11 24H2.
  2. Prioritize patching because CISA lists this vulnerability as known to be exploited; US federal agencies had a due date of 2025-06-03.
  3. Follow the Microsoft advisory and CISA's required action: apply mitigations per vendor instructions or discontinue use if mitigations are unavailable.
  4. Limit local and interactive logon rights to trusted users to reduce who could attempt privilege escalation.
  5. Review systems for signs of compromise, such as unexpected privilege changes, since the flaw has been used in attacks.

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-20 Improper Input Validation

Questions about CVE-2025-32706

Can this be exploited remotely?
No. The attack vector is local, and the attacker needs low-privileged access to the system. The vulnerability lets that attacker elevate privileges.
Is CVE-2025-32706 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-05-13. Whether it is used in ransomware campaigns is listed as unknown.
Which update fixes it?
The fix is in the builds listed per Windows version in the CVE record, such as 10.0.19045.5854 for Windows 10 22H2 and 10.0.22621.5335 for Windows 11 22H2. Check the Microsoft advisory for the matching update.

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.