dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2026-49162

HIGH · 7.0 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.26100.8875 / 10.0.26100.33158 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click 5 weeks old

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.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1w ago

Surfaced from public web coverage — external links open in a new tab.

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 (UAF) vulnerability in the Microsoft Brokering File System allows a locally authorized attacker to manipulate memory after it has been freed, potentially achieving elevated privileges.

MitigationApply Microsoft security updates for the Brokering File System component when available; prioritize patching systems with local access vectors.

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.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269< 10.0.28000.2525
Windows Server 2025Operating system
Affected:< 10.0.26100.33158

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 number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build number
    Affected if The build number is below 10.0.26100.8875 (Windows 11 24h2/Server 2025), below 10.0.26200.8875 (Windows 11 25h2), or below 10.0.28000.2269/10.0.28000.2525 (Windows 11 26h1)
  2. Verify exact OS version via PowerShell
    Run 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer' in PowerShell to get precise version details
    Affected if The reported version falls within the affected build ranges for Windows 11 24h2, 25h2, 26h1, or Windows Server 2025
  3. Confirm Brokering File System component presence
    Check for the presence of brokfs.sys or brokering file system related drivers in the system by examining C:\Windows\System32\drivers or running 'driverquery /v | findstr -i brok'
    Affected if The Brokering File System driver is present on the system (required for the vulnerability to be exploitable)

The system is affected if it runs a Windows 11 24h2/25h2/26h1 or Windows Server 2025 build number below the fixed thresholds AND has the 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.26100.8875 / 10.0.26100.33158 / 10.0.26200.8875 or later
Fixed in 10.0.26100.887510.0.26100.3315810.0.26200.8875
Interim mitigation

Apply Microsoft security updates for the Brokering File System component when available; prioritize patching systems with local access vectors.

Recommended fix High confidence

Apply Microsoft security updates via Windows Update - install the KB that addresses CVE-2026-49162

  1. Open Windows Settings on the affected system
  2. Navigate to Windows Update (Settings > Windows Update)
  3. Click 'Check for updates' to download and install the latest security updates
  4. Ensure the update includes the patch for CVE-2026-49162
  5. Restart the system if prompted to complete the installation
  6. Verify the installed version matches or exceeds the fixed version for your Windows edition (Windows 11 24h2: 10.0.26100.8875, Windows 11 25h2: 10.0.26200.8875, Windows 11 26h1: 10.0.28000.2525, Windows Server 2025: 10.0.26100.33158)
Caveat Standard Windows update.apply risks (update may require restart, minor compatibility issues rare but 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-2026-49162 — 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-49162 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