dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Jun 2025.
Windows 10 1507Operating system · Microsoft

CVE-2025-32701

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.10240.21014 / 10.0.14393.8066 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Use-after-free vulnerability in the Windows Common Log File System (CLFS) driver allows a local authenticated attacker to elevate privileges to SYSTEM level by exploiting improper memory management in the kernel-mode driver.

MitigationApply the Microsoft security update for CVE-2025-32701 to patch the CLFS driver vulnerability. As a local privilege escalation, limit local user permissions and monitor for privilege escalation attempts until patching is complete.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.21014
Windows 10 1607Operating system
Affected:< 10.0.14393.8066
Windows 10 1809Operating system
Affected:< 10.0.17763.7314
Windows 10 21h2Operating system
Affected:< 10.0.19044.5854
Windows 10 22h2Operating system
Affected:< 10.0.19045.5854
Windows 11 22h2Operating system
Affected:< 10.0.22621.5335
Windows 11 23h2Operating system
Affected:< 10.0.22631.5335
Windows 11 24h2Operating system
Affected:< 10.0.26100.3981

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the Windows build version
    Affected if The build number falls below the threshold for your Windows version (e.g., 10240.21014 for 1507, 14393.8066 for 1607, 17763.7314 for 1809, 19044.5854/19045.5854 for 10 21h2/22h2, 22621.5335 for 11 22h2, 22631.5335 for 11 23h2, 26100.3981 for 11 24h2)
  2. Verify CLFS driver presence
    Check that clfs.sys exists at %SystemRoot%\System32\drivers\clfs.sys
    Affected if The driver file is present (required for the vulnerability to apply)
  3. Check CLFS driver file version
    Right-click clfs.sys, select Properties, then Details; or run 'powershell (Get-Item C:\Windows\System32\drivers\clfs.sys).VersionInfo' to retrieve the driver version
    Affected if The driver version is lower than the patched version corresponding to your Windows build

You are affected if your Windows build number is below the version threshold for your specific Windows release and the clfs.sys driver is present on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.21014 / 10.0.14393.8066 / 10.0.17763.7314 or later
Fixed in 10.0.10240.2101410.0.14393.806610.0.17763.7314
Interim mitigation

Apply the Microsoft security update for CVE-2025-32701 to patch the CLFS driver vulnerability. As a local privilege escalation, limit local user permissions and monitor for privilege escalation attempts until patching is complete.

Recommended fix High confidence

Update to the specific fixed build for your Windows version: Windows 10 1507 to build 10.0.10240.21014, Windows 10 1607 to build 10.0.14393.8066, Windows 10 1809 to build 10.0.17763.7314, Windows 10 21h2 to build 10.0.19044.5854, Windows 10 22h2 to build 10.0.19045.5854, Windows 11 22h2 to build 10.

  1. Check current Windows version by running 'winver' or going to Settings > System > About
  2. Open Windows Update by going to Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Restart the system when prompted to complete the installation
  5. Verify the update was installed by checking Windows Update history for the relevant KB patch (refer to Microsoft Security Guide for KB number)
Caveat Standard Windows security update - minimal risk; standard practice to test business-critical applications after any OS update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32701 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32701 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data