dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2026-25167

HIGH · 7.4 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.26100.7979 / 10.0.26100.32463 or later.
See remediation →
79/100
Remediation priority · High
No privileges 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

A use-after-free vulnerability in the Microsoft Brokering File System allows a local attacker to manipulate memory after it has been freed, potentially achieving elevated privileges on the affected system.

MitigationApply the applicable Microsoft security update for this vulnerability once released. Monitor Microsoft Security Response Center for patch availability.

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.7979
Windows 11 25h2Operating system
Affected:< 10.0.26200.7979
Windows 11 26h1Operating system
Affected:< 10.0.28000.1719
Windows Server 2025Operating system
Affected:< 10.0.26100.32463

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

CVSS:3.1/AV:L/AC:H/PR:N/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. Retrieve Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"Version"' to display the installed Windows version and build number
    Affected if The displayed build number falls below the thresholds for your Windows edition (10.0.26100.7979 for 24h2, 10.0.26200.7979 for 25h2, 10.0.28000.1719 for 26h1, or 10.0.26100.32463 for Server 2025)
  2. Identify exact Windows edition
    Run 'winver' or check System Properties to confirm whether the system is Windows 11 24h2, Windows 11 25h2, Windows 11 26h1, or Windows Server 2025
    Affected if The system runs any of these four editions and the build number is below the corresponding threshold listed in step 1
  3. Verify build number programmatically
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' in Command Prompt to get the numeric build number, then check the 'DisplayVersion' value if present to identify the feature update (24h2, 25h2, 26h1)
    Affected if The build number retrieved is lower than the applicable threshold for the detected Windows edition

A system is affected if it runs Windows 11 24h2, 25h2, 26h1, or Windows Server 2025 with a build number lower than the respective threshold (10.0.26100.7979, 10.0.26200.7979, 10.0.28000.1719, or 10.0.26100.32463).

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.7979 / 10.0.26100.32463 / 10.0.26200.7979 or later
Fixed in 10.0.26100.797910.0.26100.3246310.0.26200.7979
Interim mitigation

Apply the applicable Microsoft security update for this vulnerability once released. Monitor Microsoft Security Response Center for patch availability.

Recommended fix High confidence

Windows 11 24h2: build 10.0.26100.7979 or later | Windows 11 25h2: build 10.0.26200.7979 or later | Windows 11 26h1: build 10.0.28000.1719 or later | Windows Server 2025: build 10.0.26100.32463 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 Windows security updates for your version
  4. Restart the system when prompted
  5. Verify the installed version meets the minimum build number: Windows 11 24h2 should be >=10.0.26100.7979, Windows 11 25h2 should be >=10.0.26200.7979, Windows 11 26h1 should be >=10.0.28000.1719, Windows Server 2025 should be >=10.0.26100.32463

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 / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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