dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2026-32219

HIGH · 7.0 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.26100.8246 / 10.0.26100.32690 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
Double free 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 double-free memory corruption vulnerability in the Microsoft Brokering File System (a Windows kernel component that handles SMB request brokering) allows a locally authenticated attacker to manipulate memory allocation patterns and achieve privilege escalation from their current authorized context to elevated SYSTEM-level privileges.

MitigationApply Microsoft security updates for CVE-2026-32219 as soon as they become available; prioritize patching endpoints that permit local user access or are multi-user systems.

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.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246
Windows 11 26h1Operating system
Affected:< 10.0.28000.1836
Windows Server 2025Operating system
Affected:< 10.0.26100.32690

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 version
    Run 'winver' from the Start menu or execute 'systeminfo' in Command Prompt and locate the 'OS Version' or 'Build' line
    Affected if The build number is below 10.0.26100.8246 on Windows 11 24h2 or Windows Server 2025, below 10.0.26200.8246 on Windows 11 25h2, or below 10.0.28000.1836 on Windows 11 26h1
  2. Confirm exact Windows edition
    Run 'winver' or check System Properties to verify the specific Windows 11 version (24h2, 25h2, or 26h1) or confirm Windows Server 2025
    Affected if The system is running an affected Windows 11 version or Windows Server 2025 with a build number below the corresponding threshold for that release
  3. Verify SMB brokering component presence
    The Brokering File System (BFS) is a kernel component included in affected Windows versions; its presence is inherent to the OS installation and does not require a separate feature check
    Affected if The system runs any affected Windows 11 or Windows Server 2025 build, as the vulnerable kernel component is present by default

A system is affected if it runs Windows 11 24h2, 25h2, 26h1, or Windows Server 2025 with a build number lower than the fixed thresholds (10.0.26100.8246, 10.0.26200.8246, 10.0.28000.1836, or 10.0.26100.32690 respectively).

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.8246 / 10.0.26100.32690 / 10.0.26200.8246 or later
Fixed in 10.0.26100.824610.0.26100.3269010.0.26200.8246
Interim mitigation

Apply Microsoft security updates for CVE-2026-32219 as soon as they become available; prioritize patching endpoints that permit local user access or are multi-user systems.

Recommended fix High confidence

Upgrade to Windows 11 24h2 build 10.0.26100.8246+, Windows 11 25h2 build 10.0.26200.8246+, Windows 11 26h1 build 10.0.28000.1836+, or Windows Server 2025 build 10.0.26100.32690+

  1. Open Settings > Windows Update and check for available updates
  2. Install the latest Windows security updates for your version
  3. Alternatively, manually verify the build number by running 'winver' in the Run dialog
  4. Confirm the installed build meets or exceeds the fixed version for your product: Windows 11 24h2 should be 10.0.26100.8246 or later, Windows 11 25h2 should be 10.0.26200.8246 or later, Windows 11 26h1 should be 10.0.28000.1836 or later, Windows Server 2025 should be 10.0.26100.32690 or later
  5. Reboot the system after applying updates

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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