dbcve.org
Windows 11 22h2Operating system · Microsoft

CVE-2025-53142

HIGH · 7.0 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.22621.5768 / 10.0.22631.5768 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 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

Use after free vulnerability in Microsoft Brokering File System that allows a locally authorized attacker to elevate privileges to higher permissions. The vulnerability involves memory corruption where memory is accessed after being freed, potentially leading to arbitrary code execution with elevated privileges.

MitigationApply Microsoft security updates for the Brokering File System component as they become available. Prioritize patching systems where untrusted local users have access.

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.5768
Windows 11 23h2Operating system
Affected:< 10.0.22631.5768
Windows 11 24h2Operating system
Affected:< 10.0.26100.4851
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1791
Windows Server 2025Operating system
Affected:< 10.0.26100.4851

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. Retrieve Windows version and build number
    Open Command Prompt or PowerShell and run `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
    Affected if Unable to determine version or build number from output
  2. Identify Windows edition family
    Check if the system is Windows 11 or Windows Server by examining the OS name from step 1. Windows 11 editions typically show 'Windows 11' in the name; Windows Server editions show 'Windows Server'
    Affected if The OS is neither Windows 11 nor Windows Server 2022/2025 family (this CVE does not apply)
  3. Compare build number against Windows 11 22h2 threshold
    If running Windows 11 22h2, verify the full build number is below 10.0.22621.5768. Run `ver` command to confirm exact build
    Affected if Running Windows 11 22h2 with build number below 10.0.22621.5768
  4. Compare build number against Windows 11 23h2 threshold
    If running Windows 11 23h2, verify the full build number is below 10.0.22631.5768
    Affected if Running Windows 11 23h2 with build number below 10.0.22631.5768
  5. Compare build number against Windows 11 24h2 or Server 2025 threshold
    If running Windows 11 24h2 or Windows Server 2025, verify the build number is below 10.0.26100.4851
    Affected if Running Windows 11 24h2 or Windows Server 2025 with build number below 10.0.26100.4851
  6. Compare build number against Windows Server 2022 23h2 threshold
    If running Windows Server 2022 23h2, verify the build number is below 10.0.25398.1791
    Affected if Running Windows Server 2022 23h2 with build number below 10.0.25398.1791

The system is affected if it runs Windows 11 22h2/23h2/24h2 or Windows Server 2022 23h2/2025 with a build number lower than the respective threshold for that version.

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.5768 / 10.0.22631.5768 / 10.0.25398.1791 or later
Fixed in 10.0.22621.576810.0.22631.576810.0.25398.1791
Interim mitigation

Apply Microsoft security updates for the Brokering File System component as they become available. Prioritize patching systems where untrusted local users have access.

Recommended fix High confidence

Windows 11 22h2: build 10.0.22621.5768 or later | Windows 11 23h2: build 10.0.22631.5768 or later | Windows 11 24h2: build 10.0.26100.4851 or later | Windows Server 2022 23h2: build 10.0.25398.1791 or later | Windows Server 2025: build 10.0.26100.4851 or later

  1. Open Settings > Windows Update and check for updates
  2. Install any available security updates for Microsoft Brokering File System (CVE-2025-53142)
  3. Restart the system if prompted
  4. Verify the update was applied by running 'winver' and confirming the build number matches or exceeds: 10.0.22621.5768 (Win 11 22h2), 10.0.22631.5768 (Win 11 23h2), 10.0.26100.4851 (Win 11 24h2/Server 2025), or 10.0.25398.1791 (Server 2022 23h2)

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

Fix this in Windows 11 22h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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