Cyber Resilience

CVE-2024-26162

Microsoft Windows 10 1507 ≤ 10.0.10240.20526

Published
12 March 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.020 79th percentile
Risk Priority 68 floored blend · peak EPSS

Summary

CVE-2024-26162 is a high-severity Incorrect Conversion between Numeric Types (CWE-681) vulnerability in Microsoft Windows 10 1507. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 21% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Microsoft ODBC Driver Remote Code Execution Vulnerability

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-29346Same product: Microsoft Windows 10 1507
CVE-2023-23401Same product: Microsoft Windows 10 1507
CVE-2023-24884Same product: Microsoft Windows 10 1507
CVE-2023-23388Same product: Microsoft Windows 10 1507
CVE-2024-21359Same product: Microsoft Windows 10 1507
CVE-2024-26200Same product: Microsoft Windows 10 1507
CVE-2024-28925Same product: Microsoft Windows 10 1507
CVE-2024-26208Same product: Microsoft Windows 10 1507
CVE-2024-26252Same product: Microsoft Windows 10 1507
CVE-2024-21360Same product: Microsoft Windows 10 1507

Affected Assets

microsoft
windows 10 1507
≤ 10.0.10240.20526 · ≤ 10.0.10240.20526
microsoft
windows 10 1607
≤ 10.0.14393.6796 · ≤ 10.0.14393.6796
microsoft
windows 10 1809
≤ 10.0.17763.5576
microsoft
windows 10 21h2
≤ 10.0.19044.4170
microsoft
windows 10 22h2
≤ 10.0.19045.4170
microsoft
windows 11 21h2
≤ 10.0.22000.2836
microsoft
windows 11 22h2
≤ 10.0.22621.3296
microsoft
windows 11 23h2
≤ 10.0.22631.3296
microsoft
windows server 2008
all versions, r2
microsoft
windows server 2012
all versions, r2
+4 more product configuration(s) — see NVD for full list

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover incorrect numeric conversions through targeted test cases.

Engineering principles can mandate safe numeric handling and range checks that structurally avoid bad conversions.

Input validation directly stops malformed or out-of-range numeric values from reaching conversion logic.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require code reviews, static analysis, and developer training that catch and prevent numeric type-conversion errors.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect numeric conversion defects before release.

prevents

Secure development lifecycle includes type-safety and conversion checks that reduce numeric truncation risks.

prevents

Application security requirements can mandate safe numeric handling and range validation.

prevents

Secure architecture principles promote strong typing and safe conversion practices.

prevents

Secure coding standards directly address correct numeric type conversions and overflow checks.

References