CVE-2024-43528

Windows Secure Kernel Mode Elevation of Privilege Vulnerability

HIGH
7.8
CVSS Score
Published: October 8, 2024 at 05:35 PM UTC
Updated: August 19, 2026 at 04:56 PM UTC
11 products affected across 1 vendorWindows Server 2019Windows 10 1809Windows Server 2022

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

Windows Secure Kernel Mode Elevation of Privilege Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.17763.641410.0.17763.0 ≤ v < 10.0.17763.653210.0.17763.0
Affected range stops below 10.0.17763.6414, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.17763.6532, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.501110.0.19044.0 ≤ v < 10.0.19044.513110.0.19044.0
Affected range stops below 10.0.19044.5011, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.19044.5131, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.501110.0.19045.0 ≤ v < 10.0.19045.513110.0.19045.0
Affected range stops below 10.0.19045.5011, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.19045.5131, so it looks safe — our inference, not a vendor statement
v < 10.0.22000.326010.0.22000.0 ≤ v < 10.0.22000.326010.0.22000.0
Affected range stops below 10.0.22000.3260, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.431710.0.22621.0 ≤ v < 10.0.22621.446010.0.22621.0
Affected range stops below 10.0.22621.4317, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.22621.4460, so it looks safe — our inference, not a vendor statement
v < 10.0.22631.431710.0.22631.0 ≤ v < 10.0.22631.446010.0.22631.0
Affected range stops below 10.0.22631.4317, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.22631.4460, so it looks safe — our inference, not a vendor statement
v < 10.0.26100.203310.0.26100.0 ≤ v < 10.0.26100.230310.0.26100.0
Affected range stops below 10.0.26100.2033, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.26100.2303, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.641410.0.17763.0 ≤ v < 10.0.17763.653210.0.17763.0
Affected range stops below 10.0.17763.6414, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.17763.6532, so it looks safe — our inference, not a vendor statement
v < 10.0.20348.276210.0.20348.0 ≤ v < 10.0.20348.284910.0.20348.0
Affected range stops below 10.0.20348.2762, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.20348.2849, so it looks safe — our inference, not a vendor statement
v < 10.0.25398.118910.0.25398.0 ≤ v < 10.0.25398.125110.0.25398.0
Affected range stops below 10.0.25398.1189, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.25398.1251, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-122NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card