CVE-2024-35250

HIGHNVD 7.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-12-16), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Exploited in the wild
7.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 25%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Windows Kernel-Mode Driver Elevation of Privilege Vulnerability

CVSS v3
7.8
EG Score
9.0(high)
EPSS
97.7%
KEV
⚠ Exploited

Published

June 11, 2024

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Jun 3, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft, cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-35250
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-35250

Vendor Advisories for CVE-2024-35250(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 0× in last 7d / 0× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 21:56 UTCEG score recompute
  2. 2026-07-22 21:56 UTCVendor advisory
  3. 2026-07-22 21:55 UTCGHSA enrichment
  4. 2026-07-22 19:40 UTCCISA KEV update
  5. 2026-07-22 18:01 UTCGHSA enrichment
  6. 2026-07-22 14:07 UTCEG score recompute
  7. 2026-07-22 14:07 UTCVendor advisory
  8. 2026-07-22 14:07 UTCGHSA enrichment
  9. 2026-07-22 14:07 UTCEPSS rescore
  10. 2026-07-22 14:07 UTCEPSS rescore
  11. 2026-07-22 14:05 UTCVendor advisory
  12. 2026-07-22 14:05 UTCGHSA enrichment
  13. 2026-07-22 14:04 UTCVendor advisory
  14. 2026-07-22 14:04 UTCGHSA enrichment
  15. 2026-07-22 14:04 UTCVendor advisory
  16. 2026-07-22 14:04 UTCGHSA enrichment
  17. 2026-07-22 14:04 UTCVendor advisory
  18. 2026-07-22 14:04 UTCGHSA enrichment
  19. 2026-07-22 14:01 UTCVendor advisory
  20. 2026-07-22 14:01 UTCGHSA enrichment
  21. 2026-07-22 14:01 UTCGHSA enrichment
  22. 2026-07-22 14:00 UTCVendor advisory
  23. 2026-07-22 14:00 UTCGHSA enrichment
  24. 2026-07-22 14:00 UTCGHSA enrichment
  25. 2026-07-22 13:59 UTCGHSA enrichment
Show 75 more
  1. 2026-07-22 13:58 UTCVendor advisory
  2. 2026-07-22 13:58 UTCGHSA enrichment
  3. 2026-07-22 13:58 UTCGHSA enrichment
  4. 2026-07-22 13:57 UTCVendor advisory
  5. 2026-07-22 13:57 UTCGHSA enrichment
  6. 2026-07-22 13:57 UTCGHSA enrichment
  7. 2026-07-22 13:56 UTCGHSA enrichment
  8. 2026-07-22 13:55 UTCVendor advisory
  9. 2026-07-22 13:55 UTCGHSA enrichment
  10. 2026-07-22 13:55 UTCGHSA enrichment
  11. 2026-07-22 13:54 UTCVendor advisory
  12. 2026-07-22 13:54 UTCGHSA enrichment
  13. 2026-07-22 13:54 UTCGHSA enrichment
  14. 2026-07-22 13:53 UTCGHSA enrichment
  15. 2026-07-22 13:52 UTCGHSA enrichment
  16. 2026-07-22 13:52 UTCGHSA enrichment
  17. 2026-07-22 13:50 UTCVendor advisory
  18. 2026-07-22 13:50 UTCGHSA enrichment
  19. 2026-07-22 13:50 UTCGHSA enrichment
  20. 2026-07-22 13:49 UTCVendor advisory
  21. 2026-07-22 13:49 UTCGHSA enrichment
  22. 2026-07-22 13:49 UTCGHSA enrichment
  23. 2026-07-22 13:48 UTCGHSA enrichment
  24. 2026-07-22 13:47 UTCVendor advisory
  25. 2026-07-22 13:47 UTCGHSA enrichment
  26. 2026-07-22 13:47 UTCGHSA enrichment
  27. 2026-07-22 13:46 UTCGHSA enrichment
  28. 2026-07-22 13:45 UTCVendor advisory
  29. 2026-07-22 13:45 UTCGHSA enrichment
  30. 2026-07-22 13:45 UTCGHSA enrichment
  31. 2026-07-22 13:45 UTCGHSA enrichment
  32. 2026-07-22 13:44 UTCGHSA enrichment
  33. 2026-07-22 13:42 UTCGHSA enrichment
  34. 2026-07-22 13:42 UTCGHSA enrichment
  35. 2026-07-22 13:40 UTCVendor advisory
  36. 2026-07-22 13:40 UTCGHSA enrichment
  37. 2026-07-22 13:40 UTCGHSA enrichment
  38. 2026-07-22 13:39 UTCVendor advisory
  39. 2026-07-22 13:39 UTCGHSA enrichment
  40. 2026-07-22 13:39 UTCGHSA enrichment
  41. 2026-07-22 13:38 UTCGHSA enrichment
  42. 2026-07-22 13:38 UTCGHSA enrichment
  43. 2026-07-22 13:36 UTCVendor advisory
  44. 2026-07-22 13:36 UTCGHSA enrichment
  45. 2026-07-22 13:35 UTCVendor advisory
  46. 2026-07-22 13:35 UTCGHSA enrichment
  47. 2026-07-22 13:35 UTCVendor advisory
  48. 2026-07-22 13:35 UTCGHSA enrichment
  49. 2026-07-22 13:33 UTCVendor advisory
  50. 2026-07-22 13:33 UTCGHSA enrichment
  51. 2026-07-22 13:32 UTCVendor advisory
  52. 2026-07-22 13:32 UTCGHSA enrichment
  53. 2026-07-22 13:31 UTCVendor advisory
  54. 2026-07-22 13:31 UTCGHSA enrichment
  55. 2026-07-22 13:31 UTCVendor advisory
  56. 2026-07-22 13:31 UTCGHSA enrichment
  57. 2026-07-22 13:29 UTCVendor advisory
  58. 2026-07-22 13:29 UTCGHSA enrichment
  59. 2026-07-22 13:28 UTCVendor advisory
  60. 2026-07-22 13:28 UTCGHSA enrichment
  61. 2026-07-22 13:27 UTCVendor advisory
  62. 2026-07-22 13:27 UTCGHSA enrichment
  63. 2026-07-22 13:26 UTCVendor advisory
  64. 2026-07-22 13:26 UTCGHSA enrichment
  65. 2026-07-22 13:26 UTCVendor advisory
  66. 2026-07-22 13:26 UTCGHSA enrichment
  67. 2026-07-22 13:24 UTCVendor advisory
  68. 2026-07-22 13:24 UTCGHSA enrichment
  69. 2026-07-22 13:23 UTCVendor advisory
  70. 2026-07-22 13:23 UTCGHSA enrichment
  71. 2026-07-22 13:22 UTCVendor advisory
  72. 2026-07-22 13:22 UTCGHSA enrichment
  73. 2026-07-22 13:21 UTCVendor advisory
  74. 2026-07-22 13:21 UTCGHSA enrichment
  75. 2026-07-22 13:21 UTCVendor advisory

Publicly available exploits

(6 references)

Working exploit code is in the public domain (1 Metasploit module) (5 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCxvalegendary/HVCIPwned
    First seen Feb 27, 2026

    CVE-2024-35250 demonstrates that HVCI is not a defense against data-only kernel exploits. As long as a driver bug provides an arbitrary R/W primitive, token swap remains a universal SYSTEM elevation technique — no code execution required.

    Open source ↗
  • GitHub PoC0xROOTPLS/GiveMeKernel
    First seen Jan 13, 2025

    CVE-2024-35250 PoC - Optimized & Condensed Form of Varwara's PoC

    Open source ↗
  • GitHub PoCyinsel/CVE-2024-35250-BOF
    First seen Nov 23, 2024

    CVE-2024-35250 的 Beacon Object File (BOF) 实现。

    Open source ↗
  • GitHub PoCro0tmylove/CVE-2024-35250-BOF
    First seen Oct 25, 2024

    Cobalt Strike 的 CVE-2024-35250 的 BOF。(请给我加个星，谢谢。)

    Open source ↗
  • GitHub PoCCrackerCat/CVE-2024-35250
    First seen Oct 14, 2024

    PoC for the Untrusted Pointer Dereference in the ks.sys driver

    Open source ↗
  • Metasploitexploit/windows/local/cve_2024_35250_ks_driver✓ verified
    First seen Jun 11, 2024

    Windows Access Mode Mismatch LPE in ks.sys

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2024-35250?
CVE-2024-35250 is a high vulnerability published on June 11, 2024. Windows Kernel-Mode Driver Elevation of Privilege Vulnerability
When was CVE-2024-35250 disclosed?
CVE-2024-35250 was first published in the National Vulnerability Database on June 11, 2024, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-35250 actively exploited?
Yes. CISA added CVE-2024-35250 to the Known Exploited Vulnerabilities catalog on December 16, 2024, affecting Microsoft Windows. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2024-35250?
CVE-2024-35250 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2024-35250?
CVE-2024-35250 affects Microsoft Windows. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2024-35250?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-35250, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-35250

Explore →

Is Your Infrastructure Affected by CVE-2024-35250?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs