dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-62470

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.14393.8688 / 10.0.17763.8146 or later.
See remediation →
80/100
Remediation priority · High
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
Heap-based buffer overflow 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

A heap-based buffer overflow vulnerability exists in the Windows Common Log File System Driver (CLFS.sys). An authorized local attacker can exploit this kernel-level flaw to elevate privileges to administrative or SYSTEM level, potentially gaining full control over the affected system.

MitigationApply the Microsoft security update for CVE-2025-62470 via Windows Update or enterprise patch management systems. Prioritize systems with direct user access as these are the primary targets for local privilege escalation.

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 1607Operating system
Affected:< 10.0.14393.8688
Windows 10 1809Operating system
Affected:< 10.0.17763.8146
Windows 10 21h2Operating system
Affected:< 10.0.19044.6691
Windows 10 22h2Operating system
Affected:< 10.0.19045.6691
Windows 11 23h2Operating system
Affected:< 10.0.22631.6345
Windows 11 24h2Operating system
Affected:< 10.0.26100.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
Windows Server 2008Operating system
Affected:all versions= r2

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
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the Windows build number
    Affected if Build number falls below the fixed version for your Windows release (e.g., < 14393.8688 for Windows 10 1607, < 17763.8146 for 1809, etc.)
  2. Check CLFS.sys file version
    Open File Explorer, navigate to C:\Windows\System32\drivers\, right-click clfs.sys, select Properties, and view the File Version on the Details tab. Alternatively, run 'powershell (Get-Item C:\Windows\System32\drivers\clfs.sys).VersionInfo'
    Affected if File version is lower than the kernel version corresponding to the fixed builds (e.g., below 10.0.14393.8688 for affected 1607 systems)
  3. Check installed security updates
    Run 'powershell Get-HotFix | Where-Object {$_.Description -match "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' to list recent security patches
    Affected if No security update corresponding to CVE-2025-62470 is installed (the specific KB number varies by Windows version)
  4. Verify kernel patch status via systeminfo
    Run 'systeminfo' and examine the 'Hotfix(s)' section at the bottom for the relevant CVE-2025-62470 patch
    Affected if The CVE-2025-62470 security update is not listed among installed hotfixes

Your system is affected if it runs a Windows version with a build number below the fixed threshold AND the CLFS.sys driver version is below the patched version, or if the CVE-2025-62470 security update is absent from installed hotfixes.

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.14393.8688 / 10.0.17763.8146 / 10.0.19044.6691 or later
Fixed in 10.0.14393.868810.0.17763.814610.0.19044.6691
Interim mitigation

Apply the Microsoft security update for CVE-2025-62470 via Windows Update or enterprise patch management systems. Prioritize systems with direct user access as these are the primary targets for local privilege escalation.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.8688 | Windows 10 1809: 10.0.17763.8146 | Windows 10 21h2: 10.0.19044.6691 | Windows 10 22h2: 10.0.19045.6691 | Windows 11 23h2: 10.0.22631.6345 | Windows 11 24h2: 10.0.26100.7392 | Windows 11 25h2: 10.0.26200.7392 | Windows Server 2008 R2: No patch available (EOL)

  1. Open Windows Update by pressing Windows Key + I, then navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security patches
  3. If updates are available, select them and click 'Install now'
  4. Restart the computer when prompted to complete the installation
  5. Verify the update was installed by checking the update history or viewing installed updates
  6. For Windows Server 2008 R2: This operating system is end-of-life and no longer receives security patches; migrate to a supported Windows Server version
Caveat Windows Server 2008 R2 has no security patch available and requires OS migration; all other affected versions can be patched via Windows Update

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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