dbcve.org
Windows 11 23h2Operating system · Microsoft

CVE-2025-62456

HIGH · 8.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.20348.4467 / 10.0.22631.6345 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Resilient File System (ReFS) allows an authorized attacker to execute code over a network.

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

Heap-based buffer overflow in Windows Resilient File System (ReFS) allows an authenticated attacker to execute arbitrary code. The vulnerability exists in the ReFS driver component and can be exploited to escalate privileges or execute code in the context of the kernel or a privileged process.

MitigationApply Microsoft security updates for CVE-2025-62456 when available; restrict access to trusted authorized users only; minimize attack surface by disabling ReFS if not required; monitor for suspicious file system operations.

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 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 2022Operating system
Affected:< 10.0.20348.4467
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.2025
Windows Server 2025Operating system
Affected:< 10.0.26100.7392

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

CVSS:3.1/AV:N/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. Determine if ReFS is in use on the system
    Open PowerShell and run: Get-Volume | Where-Object {$_.FileSystem -eq 'ReFS'} to list any volumes using ReFS, or check via: fsutil fsinfo volumeinfo C: (replace C: with any drive letter)
    Affected if Any ReFS-formatted volumes exist on the system and the Windows version falls within the affected build ranges below
  2. Check Windows 11 version and build number
    Run 'winver' or in PowerShell: [System.Environment]::OSVersion.Version and [System.Diagnostics.FileVersionInfo]::GetVersionInfo((Get-Process -Id $PID).Path).ProductVersion to get the full build (e.g., 10.0.22631.x)
    Affected if Build is below 10.0.22631.6345 for 23h2, below 10.0.26100.7392 for 24h2/Server 2025, below 10.0.26200.7392 for 25h2, or below 10.0.20348.4467 for Server 2022
  3. Check Windows Server version and build number
    Run 'systeminfo' or in PowerShell: $os = Get-CimInstance Win32_OperatingSystem; $os.Caption + ' ' + $os.BuildNumber to identify the Server version and build
    Affected if Running Windows Server 2022 with build below 10.0.20348.4467, Server 2022 23h2 below 10.0.25398.2025, or Server 2025 below 10.0.26100.7392 and ReFS is present

The system is affected if it runs any of the listed Windows versions below the specified builds AND has ReFS volumes present or the ReFS driver loaded.

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.20348.4467 / 10.0.22631.6345 / 10.0.25398.2025 or later
Fixed in 10.0.20348.446710.0.22631.634510.0.25398.2025
Interim mitigation

Apply Microsoft security updates for CVE-2025-62456 when available; restrict access to trusted authorized users only; minimize attack surface by disabling ReFS if not required; monitor for suspicious file system operations.

Recommended fix High confidence

Upgrade to the KB referenced in MSRC for CVE-2025-6246 (Windows 11 23h2: 10.0.22631.6345, Windows 11 24h2/Server 2025: 10.0.26100.7392, Windows 11 25h2: 10.0.26200.7392, Windows Server 2022: 10.0.20348.4467, Windows Server 2022 23h2: 10.0.25398.2025)

  1. 1. Check current Windows build version by running 'winver' or going to Settings > System > About
  2. 2. For Windows 11 23h2: ensure build is 10.0.22631.6345 or higher
  3. 3. For Windows 11 24h2: ensure build is 10.0.26100.7392 or higher
  4. 4. For Windows 11 25h2: ensure build is 10.0.26200.7392 or higher
  5. 5. For Windows Server 2022: ensure build is 10.0.20348.4467 or higher
  6. 6. For Windows Server 2022 23h2: ensure build is 10.0.25398.2025 or higher
  7. 7. For Windows Server 2025: ensure build is 10.0.26100.7392 or higher
  8. 8. Apply Windows updates via Settings > Windows Update > Check for updates
Caveat Standard Windows update risks apply - ensure backups and test in non-production environment before deploying broadly

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

Fix this in Windows 11 23h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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