Microsoft Windows 10 21H2/10 22H2 Mobile Broadband Driver heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $5k-$25k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Microsoft Windows 10 21H2/10 22H2. Affected is an unknown function of the component Mobile Broadband Driver. The manipulation leads to heap-based overflow. This vulnerability is uniquely identified as CVE-2026-24288. It is possible to launch the attack on the physical device. No exploit exists. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Microsoft Windows 10 21H2/10 22H2 and classified as critical. This issue affects an unknown code of the component Mobile Broadband Driver. The manipulation with an unknown input leads to a heap-based overflow vulnerability. Using CWE to declare the problem leads to CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Heap-based buffer overflow in Windows Mobile Broadband allows an unauthorized attacker to execute code with a physical attack.
The weakness was disclosed 03/10/2026 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. The identification of this vulnerability is CVE-2026-24288. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/13/2026).
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.8
VulDB Temp Score: 5.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 6.8
Vendor Vector (Microsoft): 🔒
CNA Base Score: 6.8
CNA Vector (Microsoft): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Yes
Local: Yes
Remote: No
Availability: 🔒
Status: Unproven
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Timeline
03/10/2026 VulDB entry created03/10/2026 Advisory disclosed
03/10/2026 Countermeasure disclosed
03/13/2026 VulDB entry last update
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-24288 (🔒)
GCVE (CVE): GCVE-0-2026-24288
GCVE (VulDB): GCVE-100-349997
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 03/10/2026 19:09Updated: 03/13/2026 05:19
Changes: 03/10/2026 19:09 (36), 03/10/2026 19:12 (33), 03/13/2026 05:19 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.