CVE-2025-55680
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 · uneditedTime-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 confidenceA 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.
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< 10.0.17763.7919< 10.0.19044.6456< 10.0.19045.6456< 10.0.22621.6060< 10.0.22631.6060< 10.0.26100.6899< 10.0.26200.6899< 10.0.17763.7919CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version against affected rangesRun '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
-
Verify Cloud Files Mini Filter Driver is loadedRun 'fltmc.exe filters' or check Services (services.msc) for 'Cloud Files Filter Driver' status, and run 'sc query cfids' to query the driver service stateAffected 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
-
Check driver file versionLocate 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.
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 · scoped10.0.17763.791910.0.19044.645610.0.19045.6456
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.
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. Check the current Windows build version by running 'winver' or 'systeminfo' from command prompt
- 2. Open Settings > Windows Update > Check for updates
- 3. Install any available security updates, specifically looking for updates that address the Windows Cloud Files Mini Filter Driver
- 4. After updates are installed, restart the computer to complete the remediation
- 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
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-55680 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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