How severe is CVE-2024-38106?

CVE-2024-38106 has a CVSS score of 7/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2024-38106?

CVE-2024-38106 affects the following products: microsoft windows 10 21h2, microsoft windows 10 22h2, microsoft windows 10 1507, microsoft windows 10 1607, microsoft windows 10 1809, microsoft windows 11 21h2, microsoft windows 11 22h2, microsoft windows 11 23h2, and 5 more.

How do I patch CVE-2024-38106?

Apply the microsoft windows 10 21h2 security patch or hotfix for CVE-2024-38106 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2024-38106 across my infrastructure?

Inventory every microsoft windows 10 21h2 deployment and check each version against the affected-products list above.

How do I mitigate CVE-2024-38106 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2024-38106 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2024-38106, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-38106?

CVE-2024-38106 has an EPSS (Exploit Prediction Scoring System) score of 6.3%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2024-38106 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2024-38106 (Microsoft Windows Kernel Privilege Escalation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-08-13. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-09-03. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2024-38106?

CVE-2024-38106 is classified as CWE-591 (CWE-591). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2024-38106?

CVE-2024-38106 affects microsoft windows 10 21h2; microsoft windows 10 22h2; microsoft windows 10 1507; microsoft windows 10 1607, and 9 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2024-38106 published, and has it been updated?

CVE-2024-38106 was published on August 13, 2024 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2024-38106 — Windows 10 21h2

HIGH

CVE-2024-38106 is a high-severity (CVSS 7) CWE-591 vulnerability in microsoft windows 10 21h2. It is in CISA's Known Exploited Vulnerabilities catalog (added 2024-08-13) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.

Windows Kernel Elevation of Privilege Vulnerability

Published

Aug 13, 2024

Updated

Jun 17, 2026

Affected

13 products

Patched

See advisory

Exploits

2 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2024-08-13. Federal agencies were required to remediate by 2024-09-03.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2024-38106.

EPSS Exploitation Probability

via FIRST.org ↗

6.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2024-38106 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Windows Kernel Elevation of Privilege Vulnerability

Affected Products

13 products · 13 configurations

windows 10 21h2microsoft

< 10.0.19044.4780

range

windows 10 22h2microsoft

< 10.0.19045.4780

range

windows 10 1507microsoft

< 10.0.10240.20751

range

windows 10 1607microsoft

< 10.0.14393.7259

range

windows 10 1809microsoft

< 10.0.17763.6189

range

windows 11 21h2microsoft

< 10.0.22000.3147

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Windows Kernel Elevation of Privilege Vulnerability

msrc.microsoft.comGoogle-sheetAug 2024

Windows Kernel Elevation of Privilege Vulnerability

cisa.govCISAAug 2024

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every microsoft windows 10 21h2 deployment and check each version against the affected-products list above.
Fix
Apply the microsoft windows 10 21h2 security patch or hotfix for CVE-2024-38106 on the affected version, following the vendor advisory for your exact build.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

Windows Kernel Elevation of Privilege Vulnerability

O3 Security · Runtime Protection

Is CVE-2024-38106 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works

CVE-2024-38106 — Windows 10 21h2

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2024-38106 being exploited in your environment?