Skip to content
vulnerability

CVE-2024-35250

7.8
High
KEV · Exploited in wildEPSS 25%Patch available

Windows Kernel-Mode Driver Elevation of Privilege Vulnerability

exploited
Yes, in CISA KEV since 16 Dec 2024fix by 6 Jan 2025 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 25.2%
Published 11 Jun 2024Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

triage
surface unknownruntimeWAF can block: noAV · localCWE-822· Common Weakness

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexitylowprivileges requiredlowuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2024-35250 being exploited?

Yes. CVE-2024-35250 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2024-35250?

CVE-2024-35250 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-35250?

Yes. A fix has been recorded for CVE-2024-35250. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-35250 affect?

CVE-2024-35250 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_21h2, and 10 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
microsoft:windows_10_1507microsoft:windows_10_1607microsoft:windows_10_1809microsoft:windows_10_21h2microsoft:windows_10_22h2microsoft:windows_11_21h2microsoft:windows_11_22h2microsoft:windows_11_23h2microsoft:windows_server_2008microsoft:windows_server_2012microsoft:windows_server_2016microsoft:windows_server_2019microsoft:windows_server_2022microsoft:windows_server_2022_23h2
affected versions
Microsoft Windows 10 Version 1507
  • affected>= 10.0.10240.0 and < 10.0.10240.20680
Microsoft Windows 10 Version 1607
  • affected>= 10.0.14393.0 and < 10.0.14393.7070
Microsoft Windows 10 Version 1809
  • affected>= 10.0.17763.0 and < 10.0.17763.5936
  • affected>= 10.0.0 and < 10.0.17763.5936
Microsoft Windows 10 Version 21H2
  • affected>= 10.0.19044.0 and < 10.0.19044.4529
Microsoft Windows 10 Version 22H2
  • affected>= 10.0.19045.0 and < 10.0.19045.4529
Microsoft Windows 11 version 21H2
  • affected>= 10.0.22000.0 and < 10.0.22000.3019
Microsoft Windows 11 version 22H2
  • affected>= 10.0.22621.0 and < 10.0.22621.3737
Microsoft Windows 11 version 23H2
  • affected>= 10.0.22631.0 and < 10.0.22631.3737
Microsoft Windows 11 Version 23H2
  • affected>= 10.0.22631.0 and < 10.0.22631.3737
Microsoft Windows Server 2008 R2 Service Pack 1
  • affected>= 6.1.7601.0 and < 6.1.7601.27170
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
  • affected>= 6.1.7601.0 and < 6.1.7601.27170
Microsoft Windows Server 2008 Service Pack 2
  • affected>= 6.0.6003.0 and < 6.0.6003.22720
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)
  • affected>= 6.0.6003.0 and < 6.0.6003.22720
Microsoft Windows Server 2012
  • affected>= 6.2.9200.0 and < 6.2.9200.24919
Microsoft Windows Server 2012 R2
  • affected>= 6.3.9600.0 and < 6.3.9600.22023
Microsoft Windows Server 2012 R2 (Server Core installation)
  • affected>= 6.3.9600.0 and < 6.3.9600.22023
Microsoft Windows Server 2012 (Server Core installation)
  • affected>= 6.2.9200.0 and < 6.2.9200.24919
Microsoft Windows Server 2016
  • affected>= 10.0.14393.0 and < 10.0.14393.7070
Microsoft Windows Server 2016 (Server Core installation)
  • affected>= 10.0.14393.0 and < 10.0.14393.7070
Microsoft Windows Server 2019
  • affected>= 10.0.17763.0 and < 10.0.17763.5936
Microsoft Windows Server 2019 (Server Core installation)
  • affected>= 10.0.17763.0 and < 10.0.17763.5936
Microsoft Windows Server 2022
  • affected>= 10.0.20348.0 and < 10.0.20348.2527
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • affected>= 10.0.25398.0 and < 10.0.25398.950

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Public exploit code: 1 Metasploit module · 6 GitHub proofs of concept

Metasploit
GitHub proofs of concept
+2 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 17 Dec 2024 (SSVC 2.0.3).

timeline

  1. 11 Jun 2024Published
  2. 14 Oct 2024First public exploit or proof of concept · 124 days (about 4 months) later
  3. 16 Dec 2024Added to CISA KEV (exploited in the wild) · 63 days (about 2 months) later
  4. 17 Dec 2024CISA SSVC assessment: exploitation active · 2 days later
  5. 6 Jan 2025CISA remediation due date (US federal agencies) · 19 days later
  6. 10 Aug 2026CVE record last updated · 582 days (about 2 years) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 84 days (about 3 months) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
2 references in the CVE record: 1 patch, 1 link
  • Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2024-35250
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-35250

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved