dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-59210

HIGH · 7.4 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.26100.6899 / 10.0.26200.6899 or later.
See remediation →
79/100
Remediation priority · High
No privileges 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
Windows Resilient File System (ReFS) Deduplication Service Elevation of Privilege Vulnerability

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

This is a Windows Elevation of Privilege vulnerability in the Resilient File System (ReFS) Deduplication Service. The flaw allows an authenticated attacker to gain elevated privileges by exploiting the deduplication service component of ReFS on affected Windows systems.

MitigationApply the Microsoft security update for CVE-2025-59210 once released, prioritizing systems with the ReFS deduplication feature enabled.

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 11 24h2Operating system
Affected:< 10.0.26100.6899
Windows 11 25h2Operating system
Affected:< 10.0.26200.6899
Windows Server 2025Operating system
Affected:<= 10.0.26100.6899

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

CVSS:3.1/AV:L/AC:H/PR:N/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 number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to retrieve the full build number
    Affected if Build number is below 10.0.26100.6899 for Server 2025, below 10.0.26100.6899 for Windows 11 24h2, or below 10.0.26200.6899 for Windows 11 25h2
  2. Confirm ReFS filesystem is in use
    Run 'fsutil fsinfo volumeinfo <drive-letter>:' (for example, 'fsutil fsinfo volumeinfo C:') to check if the volume uses the ReFS filesystem
    Affected if The volume reports "File System Name : ReFS" or "ReFS" as the filesystem type
  3. Verify deduplication feature is enabled
    Run 'Get-DedupVolume -Volume <drive-letter>' in PowerShell (module requires Server Manager or RSAT tools), or check via 'Deduplication' setting in the volume properties in Server Manager for Server 2025
    Affected if Deduplication is shown as enabled on any ReFS volume (Status shows "Enabled" or a deduplication schedule is configured)
  4. Check deduplication service status
    Run 'Get-Service -Name Deduplication' in PowerShell or 'sc query Deduplication' in Command Prompt to see if the Windows Server Deduplication service is installed and running
    Affected if The service exists and shows a status of Running, Stopped, or is simply present on the system

The system is affected if it runs a Windows 11 24h2, 25h2, or Server 2025 version below the fixed builds AND has ReFS deduplication feature enabled on any volume.

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.26100.6899 / 10.0.26200.6899 or later
Fixed in 10.0.26100.689910.0.26200.6899
Interim mitigation

Apply the Microsoft security update for CVE-2025-59210 once released, prioritizing systems with the ReFS deduplication feature enabled.

Recommended fix High confidence

Windows 11 24h2: build 10.0.26100.6899 or later | Windows 11 25h2: build 10.0.26200.6899 or later | Windows Server 2025: build higher than 10.0.26100.6899

  1. Open Settings > Windows Update and check for updates
  2. Install all available cumulative updates for your Windows version
  3. Restart the system when prompted to complete the update installation
  4. Verify the update installed by running 'winver' to confirm the build number matches or exceeds 10.0.26100.6899 for Windows 11 24h2/Server 2025, or 10.0.26200.6899 for Windows 11 25h2
Caveat Standard Windows update process; no known breaking changes for this security patch

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

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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