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-32706

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 Public exploit 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
Improper input validation 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 · moderate confidence

CVE-2025-32706 is a local privilege escalation vulnerability in the Windows Common Log File System Driver (CLFS.sys). The vulnerability stems from improper input validation within the kernel driver, allowing an authorized local attacker to elevate their privileges to SYSTEM level. This is a kernel-level flaw affecting Windows systems that could be exploited after gaining initial authenticated access.

MitigationApply the Microsoft security update for CVE-2025-32706 as soon as practical. As this is a kernel driver vulnerability with local privilege escalation impact, prioritize patching on systems where untrusted users have local access.

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 version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number
    Affected if The build number falls below the thresholds in the affected versions list (e.g., below 10.0.10240.21014 for Windows 10 1507, below 10.0.14393.8066 for Windows 10 1607, etc.)
  2. Verify CLFS driver presence
    Check if the clfs.sys driver exists in the system directory by running 'dir C:\Windows\System32\drivers\clfs.sys' in Command Prompt
    Affected if The clfs.sys file exists on the system (CLFS is a core Windows component and is present by default on most affected versions)
  3. Identify active CLFS log usage
    Search for .blf and .log files on the system using 'dir /s /b C:\*.blf C:\*.log 2>nul' in Command Prompt, or inspect known CLFS log paths such as '%SystemRoot%\System32\LogFiles' and application-specific directories
    Affected if CLFS log files (.blf or .log) exist on the system, indicating the Common Log File System driver is actively managing logs and the vulnerable code path could be triggered

A system is affected if its Windows build version is lower than the fixed thresholds AND the CLFS driver (clfs.sys) is present and in use 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-32706 as soon as practical. As this is a kernel driver vulnerability with local privilege escalation impact, prioritize patching on systems where untrusted users have local access.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21014 | Windows 10 1607: 10.0.14393.8066 | Windows 10 1809: 10.0.17763.7314 | Windows 10 21h2: 10.0.19044.5854 | Windows 10 22h2: 10.0.19045.5854 | Windows 11 22h2: 10.0.22621.5335 | Windows 11 23h2: 10.0.22631.5335 | Windows 11 24h2: 10.0.26100.3981 or later

  1. Verify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest cumulative update
  4. For enterprise environments, deploy the update via Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager
  5. Restart the system when prompted to complete the installation
  6. After reboot, verify the installed KB article matches the security update for CVE-2025-32706
Caveat Standard Windows cumulative update; no expected breaking changes for most workloads, but test in staging for business-critical applications

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32706 — 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-32706 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