dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-54105

HIGH · 7.0 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 10.0.25398.1849 / 10.0.26100.6508 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
Concurrent execution using shared resource with improper synchronization ('race condition') 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

A race condition vulnerability exists in Microsoft Brokering File System where improper synchronization of shared resources allows an authorized local attacker to elevate privileges to a higher level.

MitigationApply Microsoft security updates for this vulnerability promptly; limit local user access and monitor for suspicious process activity as a defensive measure until patches are deployed.

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.6508
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1849
Windows Server 2025Operating system
Affected:< 10.0.26100.6508

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. Identify Windows version and build
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the installed Windows version and build number
    Affected if The system is running Windows 11 24h2, Windows Server 2022 23h2, or Windows Server 2025 with a build number lower than the fixed versions (26100.6508 for Windows 11 24h2/Server 2025, 25398.1849 for Server 2022 23h2)
  2. Confirm the vulnerable component exists
    Check for the presence of the Microsoft Brokering File System service or driver by running 'sc query' or checking registry under HKLM\SYSTEM\CurrentControlSet\Services for Brokering File System related entries
    Affected if The Brokering File System component is installed and running on the system
  3. Review system for privilege escalation indicators
    Check for new or unexpected user accounts, group membership changes, or suspicious processes running with elevated privileges using 'net user', 'whoami /all', and Task Manager
    Affected if Unexpected accounts or processes with elevated privileges are found that were not authorized by administrators

The environment is affected if it runs an unpatched Windows 11 24h2, Server 2022 23h2, or Server 2025 build below the fixed versions AND has the Brokering File System component enabled.

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.1849 / 10.0.26100.6508 or later
Fixed in 10.0.25398.184910.0.26100.6508
Interim mitigation

Apply Microsoft security updates for this vulnerability promptly; limit local user access and monitor for suspicious process activity as a defensive measure until patches are deployed.

Recommended fix High confidence

Windows 11 24h2 build 10.0.26100.6508 or later | Windows Server 2022 23h2 build 10.0.25398.1849 or later | Windows Server 2025 build 10.0.26100.6508 or later

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Windows Update > Check for updates
  3. Install all available security updates, specifically looking for the patch addressing CVE-2025-54105
  4. Alternatively, use Windows Server Update Services (WSUS) or Microsoft Update Catalog to manually download and install the relevant security update
  5. Restart the system after installing the update
  6. Verify the installation by checking the installed updates list and confirming the version matches or exceeds 10.0.26100.6508 (Windows 11 24h2/Server 2025) or 10.0.25398.1849 (Windows Server 2022 23h2)
Caveat Standard Windows security update - minimal risk; test in staging if mission-critical environment

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

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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