dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-59189

HIGH · 7.0 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 →
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 unauthorized 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

This is a use-after-free vulnerability in Microsoft's Brokering File System (BFS), a kernel-mode component that handles file system operations. The vulnerability allows an unauthenticated local attacker to exploit freed memory to achieve arbitrary code execution and elevate privileges to SYSTEM level.

MitigationApply the Microsoft security update for this vulnerability as soon as possible, as local privilege escalation vulnerabilities can be chained with other attacks for full system compromise.

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
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 and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the Windows version and build number.
    Affected if The system shows Windows 11 version 24h2, 25h2, or Windows Server 2025 with a build number below the fixed versions.
  2. Verify exact build number
    Run 'ver' in Command Prompt or check the registry key 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' for the CurrentBuild and DisplayVersion values.
    Affected if CurrentBuild is 26100 or lower for Windows 11 24h2/Server 2025, or 26200 or lower for Windows 11 25h2.
  3. Confirm BFS component presence
    BFS (Brokering File System) is a kernel-mode component included in Windows 11 24h2 and later and Windows Server 2025. Check that the system is running one of these OS versions where BFS is present.
    Affected if The system is running Windows 11 24h2, Windows 11 25h2, or Windows Server 2025.

You are affected if your system runs Windows 11 24h2, Windows 11 25h2, or Windows Server 2025 with a build number lower than 10.0.26100.6899 (for 24h2/Server 2025) or 10.0.26200.6899 (for 25h2).

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 this vulnerability as soon as possible, as local privilege escalation vulnerabilities can be chained with other attacks for full system compromise.

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 greater than 10.0.26100.6899

  1. Open Windows Settings and navigate to Windows Update
  2. Check for updates and install all available security updates
  3. Alternatively, manually download and install the relevant cumulative security update from the Microsoft Update Catalog for your specific Windows version
  4. Restart the system after applying the update
  5. Verify the update was installed by checking the installed updates list or 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 with potential restart required; minimal risk as this is a security fix

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

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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