CyberSecBulletin
CVE-2025-32706Exploited in the wildNVD status: Analyzed

Microsoft Windows Common Log File System (CLFS) Driver Heap-Based Buffer Overflow

Published Updated By the CyberSecBulletin desk

CVE-2025-32706 is a high-severity improper input validation vulnerability in Windows 10 Version 1507 from Microsoft, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 10.0.10240.21014 as the first without the flaw, so updating Windows 10 Version 1507 to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on May 13, 2025, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update Windows 10 Version 1507 to 10.0.10240.21014 or a later version.
  2. Update Windows 10 Version 1607 to 10.0.14393.8066 or a later version.
  3. Update Windows 10 Version 1809 to 10.0.17763.7314 or a later version.
  4. CISA's 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.
  5. Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftWindows 10 Version 150710.0.10240.0 up to, but not including, 10.0.10240.2101410.0.10240.21014
MicrosoftWindows 10 Version 160710.0.14393.0 up to, but not including, 10.0.14393.806610.0.14393.8066
MicrosoftWindows 10 Version 180910.0.17763.0 up to, but not including, 10.0.17763.731410.0.17763.7314
MicrosoftWindows 10 Version 21H210.0.19044.0 up to, but not including, 10.0.19044.585410.0.19044.5854
MicrosoftWindows 10 Version 22H210.0.19045.0 up to, but not including, 10.0.19045.585410.0.19045.5854
MicrosoftWindows 11 version 22H210.0.22621.0 up to, but not including, 10.0.22621.533510.0.22621.5335
MicrosoftWindows 11 version 22H310.0.22631.0 up to, but not including, 10.0.22631.533510.0.22631.5335
MicrosoftWindows 11 Version 23H210.0.22631.0 up to, but not including, 10.0.22631.533510.0.22631.5335
MicrosoftWindows 11 Version 24H210.0.26100.0 up to, but not including, 10.0.26100.406110.0.26100.4061
MicrosoftWindows Server 2008 R2 Service Pack 16.1.7601.0 up to, but not including, 6.1.7601.277296.1.7601.27729
MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)6.1.7601.0 up to, but not including, 6.1.7601.277296.1.7601.27729
MicrosoftWindows Server 2008 Service Pack 26.0.6003.0 up to, but not including, 6.0.6003.232796.0.6003.23279
MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)6.0.6003.0 up to, but not including, 6.0.6003.232796.0.6003.23279
MicrosoftWindows Server 20126.2.9200.0 up to, but not including, 6.2.9200.254756.2.9200.25475
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0 up to, but not including, 6.2.9200.254756.2.9200.25475
MicrosoftWindows Server 2012 R26.3.9600.0 up to, but not including, 6.3.9600.225776.3.9600.22577
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0 up to, but not including, 6.3.9600.225776.3.9600.22577
MicrosoftWindows Server 201610.0.14393.0 up to, but not including, 10.0.14393.806610.0.14393.8066
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0 up to, but not including, 10.0.14393.806610.0.14393.8066
MicrosoftWindows Server 201910.0.17763.0 up to, but not including, 10.0.17763.731410.0.17763.7314
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0 up to, but not including, 10.0.17763.731410.0.17763.7314
MicrosoftWindows Server 202210.0.20348.0 up to, but not including, 10.0.20348.369210.0.20348.3692
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0 up to, but not including, 10.0.25398.161110.0.25398.1611
MicrosoftWindows Server 202510.0.26100.0 up to, but not including, 10.0.26100.406110.0.26100.4061
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0 up to, but not including, 10.0.26100.406110.0.26100.4061

Version data comes from the organisation that assigned the CVE; 10 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).

Official description

Improper input validation in Windows Common Log File System Driver allows an authorized attacker to elevate privileges locally.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. Added to CISA's Known Exploited Vulnerabilities catalogue.
  3. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  4. Deadline for US federal agencies to remediate, set by CISA.
  5. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Technical write-ups (may include proof of concept)

Other vulnerabilities in Windows 10 Version 1507

All Windows 10 Version 1507 vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.