dbcve.org
Windows 11 22h2Operating system · Microsoft

CVE-2025-48004

HIGH · 7.0 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.22621.6060 / 10.0.25398.1913 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
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

Use after free vulnerability in Microsoft Brokering File System allows a local unauthenticated attacker to elevate privileges to higher integrity levels.

MitigationApply the Microsoft security update addressing CVE-2025-48004 through Windows Update or enterprise patch management 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 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899
Windows 11 25h2Operating system
Affected:< 10.0.26200.6899
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1913
Windows Server 2025Operating system
Affected:<= 10.0.26100.6899

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 version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full version and build number
    Affected if The displayed build number is lower than any of the following: 22621.6060 (Win11 22h2), 22631.6060 (Win11 23h2), 26100.6899 (Win11 24h2/Server 2025), 26200.6899 (Win11 25h2), or 25398.1913 (Server 2022 23h2)
  2. Verify Windows edition matches affected product line
    Run 'systeminfo' and check if the OS Name indicates Windows 11 or Windows Server 2022/2025
    Affected if The system is running Windows 11 (any version) or Windows Server 2022/2025 and the build number falls below the thresholds listed in step 1
  3. Confirm Microsoft Brokering File System component presence
    Check for the presence of the 'mrxdav.sys' or related brokering file system drivers by running 'sc query mrxsmb20' or examining C:\Windows\System32\drivers for 'mrxdav*' files
    Affected if The Microsoft Brokering File System component (mrxdav.sys or similar) is present on the system, which is default in affected Windows versions

A system is affected if it runs any of the listed Windows 11 or Windows Server versions with a build number below the specified thresholds, indicating the unpatched version of the Microsoft Brokering File System is 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.22621.6060 / 10.0.25398.1913 / 10.0.26100.6899 or later
Fixed in 10.0.22621.606010.0.25398.191310.0.26100.6899
Interim mitigation

Apply the Microsoft security update addressing CVE-2025-48004 through Windows Update or enterprise patch management systems.

Recommended fix High confidence

Install the latest Windows Security Update containing the CVE-2025-48004 patch for your specific Windows version

  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 fix for CVE-2025-48004 (Microsoft Brokering File System Use After Free)
  5. Restart the system if prompted to complete the installation
  6. Verify the installed Windows version matches or exceeds the fixed build numbers: 10.0.22621.6060 (22h2), 10.0.22631.6061+ (23h2), 10.0.26100.6899 (24h2), 10.0.26200.6899 (25h2), 10.0.25398.1913 (Server 2022), or 10.0.26100.6900+ (Server 2025)
Caveat Standard Windows update; no breaking changes expected for this security patch

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

Fix this in Windows 11 22h2 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-48004 — 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-48004 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