dbcve.org
Windows 10 21h2Operating system · Microsoft

CVE-2026-24288

MEDIUM · 6.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.19044.7058 / 10.0.19045.7058 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges 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
Heap-based buffer overflow in Windows Mobile Broadband allows an unauthorized attacker to execute code with a physical attack.

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 heap-based buffer overflow vulnerability exists in Windows Mobile Broadband that allows an unauthorized attacker to execute arbitrary code. The vulnerability requires physical access to the target device for exploitation, which distinguishes it from purely remote vulnerabilities.

MitigationApply available Microsoft security patches for Windows Mobile Broadband and ensure Windows systems are kept current through standard patch management processes.

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 21h2Operating system
Affected:< 10.0.19044.7058
Windows 10 22h2Operating system
Affected:< 10.0.19045.7058

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

CVSS:3.1/AV:P/AC:L/PR:N/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 build number
    Run 'winver' from command prompt or 'systeminfo' and look at the OS Build value. Alternatively, run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' to get the numeric build.
    Affected if The build number is less than 19044.7058 for Windows 10 21h2, or less than 19045.7058 for Windows 10 22h2.
  2. Confirm Windows 10 feature update version
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v DisplayVersion' to see if it shows 21H2 or 22H2, or check the UBR value in the same registry key.
    Affected if The system is running Windows 10 21H2 or 22H2 with a build number below the patched thresholds.
  3. Verify Windows Mobile Broadband component exists
    Check for the presence of Mobile Broadband infrastructure: run 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Mobile Broadband"' or look for mbbmux.dll in C:\Windows\System32 using 'dir C:\Windows\System32\mbb*.dll'.
    Affected if The Mobile Broadband component is present on the system, making it a potential target.
  4. Check for mobile broadband devices
    Open Device Manager (devmgmt.msc) and look under 'Network adapters' for any Mobile Broadband devices such as 'Mobile Broadband GPS Enumerator' or similar mobile broadband adapters.
    Affected if A mobile broadband adapter or related device is installed and enabled.

A user is affected if they are running Windows 10 21H2 or 22H2 with a build below 19044.7058 or 19045.7058 respectively, AND the Windows Mobile Broadband component is present on their system.

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.19044.7058 / 10.0.19045.7058 or later
Fixed in 10.0.19044.705810.0.19045.7058
Interim mitigation

Apply available Microsoft security patches for Windows Mobile Broadband and ensure Windows systems are kept current through standard patch management processes.

Recommended fix Moderate confidence

Windows 10 21h2: build 10.0.19044.7058 or later | Windows 10 22h2: build 10.0.19045.7058 or later

  1. Identify your current Windows 10 version (21h2 or 22h2) by running 'winver' or checking Settings > System > About
  2. For Windows 10 21h2: Apply Windows 10 cumulative update KBxxxxxxx that includes build 10.0.19044.7058 or later
  3. For Windows 10 22h2: Apply Windows 10 cumulative update KBxxxxxxx that includes build 10.0.19045.7058 or later
  4. Verify the update was successful by checking the Windows version matches or exceeds the target build number
  5. Restart the system if prompted to complete the update installation
Caveat Standard Windows update risks apply - ensure critical data is backed up before applying updates

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

Fix this in Windows 10 21h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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