dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-55230

HIGH · 7.8 CVSS v3.1 Published 2025-08-21
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 or later.
See remediation →
80/100
Remediation priority · High
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
Untrusted pointer dereference in Windows MBT Transport driver 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

An untrusted pointer dereference vulnerability exists in the Windows MBT (Message Bus Transport) driver. The driver fails to properly validate user-supplied pointers before dereferencing them, allowing a local authenticated attacker to execute arbitrary code in kernel mode and elevate privileges to SYSTEM level.

MitigationApply the Microsoft security update for CVE-2025-55230 through Windows Update or enterprise patch management systems. Prioritize workstations and servers running the affected MBT Transport driver component.

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 10 1507Operating system
Affected:< 10.0.10240.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

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

CVSS:3.1/AV:L/AC:L/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. Identify installed Windows version
    Run 'winver' from the Run dialog, or use 'systeminfo' in Command Prompt, or check Settings > System > About. Record the full version number and build.
    Affected if The version falls below any of these thresholds: Windows 10 1507 < 10.0.10240.21073, Windows 10 1607 < 10.0.14393.8246, Windows 10 1809 < 10.0.17763.7558, Windows 10 21h2 < 10.0.19044.6093, Windows 10 22h2 < 10.0.19045.6093, Windows 11 22h2 < 10.0.22621.5624, Windows 11 23h2 < 10.0.22631.5624, Windo
  2. Locate the MBT driver file
    Search for 'mbt' driver files in C:\Windows\System32\drivers\ or use PowerShell command: Get-ChildItem -Path C:\Windows\System32\drivers\ -Filter *mbt* -ErrorAction SilentlyContinue
    Affected if The MBT driver file exists on the system, indicating the vulnerable component is present
  3. Verify MBT driver is loaded
    Run 'driverquery /v | findstr mbt' in Command Prompt, or use 'Get-Process' in PowerShell to check for loaded kernel drivers containing 'mbt' in the name
    Affected if The MBT driver shows as loaded or running in driver query results, meaning the attack surface is active

If your Windows version is below the specified build numbers for your release and the MBT driver is present and loaded on the system, you are affected by this vulnerability.

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.10240.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply the Microsoft security update for CVE-2025-55230 through Windows Update or enterprise patch management systems. Prioritize workstations and servers running the affected MBT Transport driver component.

Recommended fix High confidence

Windows 10 1507: build 10.0.10240.21073 or later | Windows 10 1607: build 10.0.14393.8246 or later | Windows 10 1809: build 10.0.17763.7558 or later | Windows 10 21h2: build 10.0.19044.6093 or later | Windows 10 22h2: build 10.0.19045.6093 or later | Windows 11 22h2: build 10.0.22621.5624 or later |

  1. 1. Identify the current Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows 10 or 11 version and build is installed (1507, 1607, 1809, 21h2, 22h2, 22h2, 23h2, or 24h2)
  3. 3. Open Windows Settings > Update & Security > Windows Update
  4. 4. Click 'Check for updates' to download and install the latest cumulative security update
  5. 5. Alternatively, manually download the appropriate security update from the Microsoft Update Catalog (https://catalog.update.microsoft.com) for the specific Windows version
  6. 6. After installation, restart the system to apply the kernel driver update
  7. 7. Verify the fix by running 'winver' and confirming the build number meets or exceeds the fixed version for your Windows release
Caveat Standard Windows cumulative update apply; no expected breaking changes for this security patch

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

Fix this in Windows 10 1507 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-2025-55230 — 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-55230 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