Windows 10 1809Operating system · Microsoft

CVE-2025-55680

HIGH · 7.0 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.17763.7919 / 10.0.19044.6456 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Time-of-check time-of-use (toctou) race condition in Windows Cloud Files Mini Filter 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 time-of-check time-of-use (TOCTOU) race condition exists in the Windows Cloud Files Mini Filter Driver. The vulnerability allows a locally authorized attacker to exploit the timing gap between when a security check is performed and when the checked resource is actually used, enabling local privilege escalation.

MitigationApply the Microsoft security update addressing CVE-2025-55680 when available. Until the patch is applied, limit local administrative access and monitor for suspicious processes interacting with the Cloud Files Mini Filter Driver.

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 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:< 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899
Windows 11 25h2Operating system
Affected:< 10.0.26200.6899
Windows Server 2019Operating system
Affected:< 10.0.17763.7919

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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 version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' and identify the exact build number (e.g., 10.0.17763.x for Windows 10 1809/Server 2019, 10.0.19044.x for Windows 10 21h2, etc.)
    Affected if The installed Windows build number is lower than 10.0.17763.7919 (Windows 10 1809/Server 2019), 10.0.19044.6456 (Windows 10 21h2), 10.0.19045.6456 (Windows 10 22h2), 10.0.22621.6060 (Windows 11 22h2), 10.0.22631.6060 (Windows 11 23h2), 10.0.26100.6899 (Windows 11 24h2), or 10.0.26200.6899 (Windows 1
  2. Verify Cloud Files Mini Filter Driver is loaded
    Run 'fltmc.exe filters' or check Services (services.msc) for 'Cloud Files Filter Driver' status, and run 'sc query cfids' to query the driver service state
    Affected if The Cloud Files Mini Filter Driver (cfids.sys) is present and running on the system - the vulnerability exists only when this driver is loaded and active
  3. Check driver file version
    Locate the driver file at %SystemRoot%\System32\drivers\cfids.sys, right-click Properties > Details to view File Version, or run 'powershell (Get-Item C:\Windows\System32\drivers\cfids.sys).VersionInfo.FileVersion'
    Affected if The cfids.sys file version is lower than the build numbers listed in the affected version ranges for your Windows version

You are affected if your Windows build version falls within any of the affected ranges AND the Cloud Files Mini Filter Driver (cfids.sys) is loaded on your 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.17763.7919 / 10.0.19044.6456 / 10.0.19045.6456 or later
Fixed in 10.0.17763.791910.0.19044.645610.0.19045.6456
Interim mitigation

Apply the Microsoft security update addressing CVE-2025-55680 when available. Until the patch is applied, limit local administrative access and monitor for suspicious processes interacting with the Cloud Files Mini Filter Driver.

Recommended fix High confidence

Windows security update matching or exceeding the build versions listed above for your specific Windows version (e.g., Windows 10 22h2 build 10.0.19045.6456 or later)

  1. 1. Check the current Windows build version by running 'winver' or 'systeminfo' from command prompt
  2. 2. Open Settings > Windows Update > Check for updates
  3. 3. Install any available security updates, specifically looking for updates that address the Windows Cloud Files Mini Filter Driver
  4. 4. After updates are installed, restart the computer to complete the remediation
  5. 5. Verify the fix by checking the installed Windows build version matches or exceeds: Windows 10 1809/Server 2019: 10.0.17763.7919, Windows 10 21h2: 10.0.19044.6456, Windows 10 22h2: 10.0.19045.6456, Windows 11 22h2: 10.0.22621.6060, Windows 11 23h2: 10.0.22631.6060, Windows 11 24h2: 10.0.26100.6899, Windows 11 25h2: 10.0.26200.6899
Caveat Standard Windows security updates typically have no breaking changes; always test updates in a non-production environment first

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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