dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-49694

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.25398.1732 / 10.0.26100.4652 or later.
See remediation →
80/100
Remediation priority · High
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
Null pointer dereference 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 null pointer dereference vulnerability exists in the Microsoft Brokering File System component that allows an authenticated local attacker to execute code with elevated privileges. The flaw occurs when the system improperly handles certain file system operations, leading to the null pointer condition that can be exploited for local privilege escalation.

MitigationApply Microsoft security updates for Windows that address the Microsoft Brokering File System vulnerability. Organizations should prioritize patching endpoints given the local privilege escalation vector.

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.4652
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1732
Windows Server 2025Operating system
Affected:< 10.0.26100.4652

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

CVSS:3.1/AV:L/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. Identify Windows version and build
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the installed Windows edition and build number
    Affected if The system is Windows 11 24h2, Windows Server 2022 23h2, or Windows Server 2025 with a build number lower than 10.0.26100.4652 (for 11/Server 2025) or 10.0.25398.1732 (for Server 2022 23h2)
  2. Confirm the specific Windows edition
    Check if the system is running one of the affected editions: Windows 11 version 24h2, Windows Server 2022 (23h2), or Windows Server 2025
    Affected if The system is running any of these three specific editions with a vulnerable build number
  3. Check for the Brokering File System component
    Verify the presence of the Microsoft Brokering File System component on the system - this component must be present for the vulnerability to be exploitable
    Affected if The Brokering File System component is loaded or enabled on the system and the build version falls within the affected range

A system is affected if it runs Windows 11 24h2, Windows Server 2022 23h2, or Windows Server 2025 with a build number below the fixed thresholds (10.0.26100.4652 or 10.0.25398.1732 respectively) and has the Microsoft Brokering File System component present.

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.1732 / 10.0.26100.4652 or later
Fixed in 10.0.25398.173210.0.26100.4652
Interim mitigation

Apply Microsoft security updates for Windows that address the Microsoft Brokering File System vulnerability. Organizations should prioritize patching endpoints given the local privilege escalation vector.

Recommended fix High confidence

Windows 11 24h2: build 10.0.26100.4652 or later | Windows Server 2022 23h2: build 10.0.25398.1732 or later | Windows Server 2025: build 10.0.26100.4652 or later

  1. Open Windows Settings and navigate to Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Restart the system when prompted to complete the installation
  4. Verify the installation by checking the Windows version: Run 'winver' command and confirm the build number matches or exceeds 10.0.26100.4652 for Windows 11 24h2/Server 2025, or 10.0.25398.1732 for Windows Server 2022 23h2
Caveat Standard Windows update risks apply (potential for compatibility issues with third-party software; test in staging if possible)

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-49694 — 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-49694 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