dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-47996

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
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
Integer underflow (wrap or wraparound) 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

Integer underflow in Windows MBT Transport driver allows local privilege escalation. The vulnerability stems from improper bounds checking in arithmetic operations within the driver, potentially enabling an authorized attacker to corrupt memory and elevate privileges to SYSTEM level.

MitigationApply the Microsoft security update for CVE-2025-47996 via Windows Update or Microsoft Update Catalog once released. Verify the MBT Transport driver version post-patch.

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 the MBT Transport driver on the system
    Open Command Prompt or PowerShell and run: driverquery /v | findstr -i MBT to list the MBT Transport driver if present. Alternatively, check for files named mbt*.sys in C:\Windows\System32\drivers\
    Affected if No MBT Transport driver is found on the system, meaning the vulnerability does not apply
  2. Retrieve the MBT Transport driver version
    If the driver is present, right-click the driver file (such as mbt.sys) in C:\Windows\System32\drivers\, select Properties, and view the File Version field. Alternatively, run: powershell (Get-Item 'C:\Windows\System32\drivers\mbt.sys').VersionInfo
    Affected if The driver version is lower than the safe version numbers listed for your Windows version (10.0.10240.21073 for 1507, 10.0.14393.8246 for 1607, 10.0.17763.7558 for 1809, 10.0.19044.6093 for 21h2, 10.0.19045.6093 for 22h2, 10.0.22621.5624 for Win11 22h2, 10.0.22631.5624 for Win11 23h2, 10.0.26100.465
  3. Confirm the Windows version installed
    Run winver from the Run dialog, or run: powershell [System.Environment]::OSVersion.Version to get the exact Windows build number
    Affected if The Windows build number falls within the affected ranges and matches a version that requires the patch based on the driver version found in step 2
  4. Verify if the MBT Transport driver is currently loaded
    Run: powershell Get-Process | Where-Object {$_.Modules.ModuleName -like '*mbt*'} or check in Device Manager under System Devices for the MBT Transport driver status
    Affected if The driver is loaded and its version is below the safe threshold for your Windows build, indicating the vulnerability is present and exploitable

A user is affected if the MBT Transport driver is present on their Windows system with a version lower than the safe threshold corresponding to their Windows build number.

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-47996 via Windows Update or Microsoft Update Catalog once released. Verify the MBT Transport driver version post-patch.

Recommended fix High confidence

Upgrade to the minimum fixed build for your Windows version: 10.0.10240.21073 (Win10 1507), 10.0.14393.8246 (Win10 1607), 10.0.17763.7558 (Win10 1809), 10.0.19044.6093 (Win10 21h2), 10.0.19045.6093 (Win10 22h2), 10.0.22621.5624 (Win11 22h2), 10.0.22631.5624 (Win11 23h2), or 10.0.26100.4652 (Win11 24

  1. Identify the current Windows version and build by running `winver` or checking Settings > System > About
  2. Determine which Windows version branch you are on (1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2/23h2/24h2)
  3. Open Windows Update (Settings > Update & Security > Windows Update) and check for updates
  4. Install the latest cumulative security update for your specific Windows version
  5. Verify the update was installed by checking the build number matches or exceeds the fixed version for your branch: 10.0.10240.21073 (1507), 10.0.14393.8246 (1607), 10.0.17763.7558 (1809), 10.0.19044.6093 (21h2), 10.0.19045.6093 (22h2), 10.0.22621.5624 (Win11 22h2), 10.0.22631.5624 (Win11 23h2), or 10.0.26100.4652 (Win11 24h2)
  6. Reboot the system as prompted to complete the update installation
Caveat Standard Windows update risks apply; major version upgrades may require application compatibility testing

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
  • 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-2025-47996 — 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-47996 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