CVE Intelligence
CISA KEV High Memory corruption exploit reference

CVE-2024-21338 — Microsoft Windows Kernel Exposed IOCTL with Insufficient Access Control Vulnerability

Windows Kernel Elevation of Privilege Vulnerability

Published Feb 13, 2024 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: microsoft

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Used in ransomware campaigns (CISA)+10
  • Public exploit/PoC (exploitdb, github)+14
  • EPSS 59.8% (30-day exploitation probability)+15
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Mar 4, 2024
EPSS FIRST
59.81%
ahead of 99% of scored CVEs · Oct 15, 2026
Affects
Microsoft
Windows 10 1809 and 17 more
CVSS base
7.8
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

CISA required action CISA

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

US federal deadline: Mar 25, 2024 — passed 935 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Microsoft Windows 10 1809 < 10.0.17763.5458 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 21h2 < 10.0.19044.4046 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 22h2 < 10.0.19045.4046 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 Version 1809 ≥ 10.0.0 and < 10.0.17763.5458≥ 10.0.17763.0 and < 10.0.17763.5458 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 21H2 ≥ 10.0.19043.0 and < 10.0.19044.4046 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 22H2 ≥ 10.0.19045.0 and < 10.0.19045.4046 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 21h2 < 10.0.22000.2777 Vulnerable NIST National Vulnerability Database
Microsoft Windows 11 22h2 < 10.0.22621.3155 Vulnerable NIST National Vulnerability Database
Microsoft Windows 11 23h2 < 10.0.22631.3155 Vulnerable NIST National Vulnerability Database
Microsoft Windows 11 version 21H2 ≥ 10.0.0 and < 10.0.22000.2777 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 version 22H2 ≥ 10.0.22621.0 and < 10.0.22621.3155 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 version 22H3 ≥ 10.0.22631.0 and < 10.0.22631.3155 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 version 23H2 ≥ 10.0.22631.0 and < 10.0.22631.3155 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2019 ≥ 10.0.17763.0 and < 10.0.17763.5458 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2019 < 10.0.17763.5458 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2019 (Server Core installation) ≥ 10.0.17763.0 and < 10.0.17763.5458 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2022 ≥ 10.0.20348.0 and < 10.0.20348.2322 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2022 < 10.0.20348.2322 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2022 23h2 ≤ 10.0.25398.709 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) ≥ 10.0.25398.0 and < 10.0.25398.709 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.8 CVSS 3.1 High 1.8 5.9 secure@microsoft.com via NIST National Vulnerability Database
7.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.8 CVSS 3.1 High — — microsoft via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: secure@microsoft.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-822 · Untrusted Pointer Dereference

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Mar 4, 2024
Federal deadline
Mar 25, 2024
passed 935 day(s) ago
Ransomware use
Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 12, 2026 → Oct 15, 2026 · 4 reading(s) · max 59.81%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
  • Hunt retroactively in logs from before Mar 4, 2024 (KEV listing): exploitation may have started earlier.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · microsoft/windows 10 version 1809, microsoft/windows 10 version 21h2, microsoft/windows 10 version 22h2, microsoft/windo
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · microsoft/windows 10 1809, microsoft/windows 10 21h2, microsoft/windows 10 22h2, microsoft/windows 11 21h2, microsoft/wi
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2024
  • Added to CISA KEV catalog
    Mar 3, 2024 · CISA
  • CVE published
    Feb 13, 2024 · microsoft

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

9 on the record

Elsewhere on this site

Microsoft
every CVE for this vendor
2024-03
what else CISA listed that month
CWE-822
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-97844 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97839 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97840 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97841 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97842 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97843 Role: DNS Server Information Disclosure Vulnerability 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2024-21338 is "Microsoft Windows Kernel Exposed IOCTL with Insufficient Access Control Vulnerability", rated High. It affects Windows 10 1809 (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.8 describes technical severity. EPSS 59.81% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.