dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-62569

HIGH · 7.0 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.25398.2025 / 10.0.26100.7392 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
Use after free in Microsoft Brokering File System 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

Use-after-free vulnerability in Microsoft Brokering File System (BFS) enabling local privilege escalation. The flaw allows an authorized attacker to manipulate freed memory to execute arbitrary code with elevated privileges.

MitigationApply Microsoft security updates for CVE-2025-62569 immediately. Prioritize domain controllers and systems with sensitive data or external attack exposure.

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.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
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
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 build version
    Run 'systeminfo' or 'winver' and locate the OS Build number in the format 10.0.XXXXX.XXXX
    Affected if The build number is less than 26100.7392 on Windows 11 24h2 or Windows Server 2025, less than 26200.7392 on Windows 11 25h2, or less than 25398.2025 on Windows Server 2022 23h2
  2. Confirm Windows edition and build mapping
    Run 'winver' to confirm exact Windows edition (e.g., Windows 11 24h2, Windows 11 25h2, Windows Server 2022 23h2, or Windows Server 2025)
    Affected if The edition matches an affected version listed in the CVE and the build number falls below the corresponding threshold
  3. Verify Brokering File System component presence
    Check for BFS driver by running 'sc query bfs' or checking C:\Windows\System32\drivers\bfs.sys existence
    Affected if The BFS driver service exists or the bfs.sys file is present on the system

A system is affected if it runs an affected Windows edition with a build number below the specified threshold AND has the Brokering File System component present on the 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.25398.2025 / 10.0.26100.7392 / 10.0.26200.7392 or later
Fixed in 10.0.25398.202510.0.26100.739210.0.26200.7392
Interim mitigation

Apply Microsoft security updates for CVE-2025-62569 immediately. Prioritize domain controllers and systems with sensitive data or external attack exposure.

Recommended fix High confidence

Windows 11 24h2: build 10.0.26100.7392+ | Windows 11 25h2: build 10.0.26200.7392+ | Windows Server 2022 23h2: build 10.0.25398.2025+ | Windows Server 2025: build 10.0.26100.7392+

  1. Open Settings > Windows Update and check for updates, or run 'winver' to confirm your current build version
  2. For Windows 11 24h2: Ensure the installed build is 10.0.26100.7392 or higher
  3. For Windows 11 25h2: Ensure the installed build is 10.0.26200.7392 or higher
  4. For Windows Server 2022 23h2: Ensure the installed build is 10.0.25398.2025 or higher
  5. For Windows Server 2025: Ensure the installed build is 10.0.26100.7392 or higher
  6. Install the applicable Windows security update containing these builds via Windows Update, WSUS, or manual KB download
  7. Restart the system as prompted to complete the update installation
  8. Verify successful installation by checking the installed updates or running 'winver' to confirm the build number matches or exceeds the required version
Caveat Standard Windows security update; may require system restart

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
  • 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-62569 — 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-62569 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