Skip to content
Server Security Center
KEVhigh7.8 Used in ransomware campaigns

CVE-2021-43226: Microsoft Windows Privilege Escalation

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-10-06.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
3.3%
higher than 88.7% of all CVEs
Added to CISA KEV
2025-10-06
US federal due date 2025-10-27
Automatable (CISA SSVC)
no
technical impact: total

CVE-2021-43226 explained

CVE-2021-43226 is a privilege escalation vulnerability in the Microsoft Windows Common Log File System Driver. It could allow a local, privileged attacker to bypass certain security mechanisms. CISA lists it as known exploited, including use in ransomware campaigns, which makes patching a priority.

Impact

An attacker who already has local access with low privileges can exploit the flaw without user interaction. Successful exploitation can lead to high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so exploitation is not expected at scale without manual steps. Attackers are known to exploit it, and CISA reports known ransomware use.

Who is affected

The CVE record lists Windows 10 Versions 1809, 1909, 2004, 20H2, 21H1 and 21H2, Windows 11 version 21H2, Windows Server 2019 (including Server Core installation), Windows Server 2022, and Windows Server versions 2004 and 20H2. Fixed builds include 10.0.17763.2366 (1809/Server 2019), 10.0.18363.1977 (1909), 10.0.19041.1415, 10.0.19042.1415, 10.0.19043.1415, 10.0.19044.1415, 10.0.20348.405 (Server 2022) and 10.0.22000.376 (Windows 11 21H2). Further products are listed on this page.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Windows Common Log File System Driver contains a privilege escalation vulnerability that could allow a local, privileged attacker to bypass certain security mechanisms.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.2366
    Fixed in
    • 10.0.17763.2366
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.2366
    Fixed in
    • 10.0.17763.2366
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.2366
    Fixed in
    • 10.0.17763.2366
  • Microsoft Windows 10 Version 190932-bit, x64, ARM64
    Affected
    • < 10.0.18363.1977
    Fixed in
    • 10.0.18363.1977
  • Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit
    Affected
    • < 10.0.19043.1415
    Fixed in
    • 10.0.19043.1415
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.405
    Fixed in
    • 10.0.20348.405
  • Microsoft Windows 10 Version 200432-bit, ARM64, x64
    Affected
    • < 10.0.19041.1415
    Fixed in
    • 10.0.19041.1415
  • Microsoft Windows Server version 2004x64
    Affected
    • < 10.0.19041.1415
    Fixed in
    • 10.0.19041.1415
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1415
    Fixed in
    • 10.0.19042.1415
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1415
    Fixed in
    • 10.0.19042.1415
Show 17 more products
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.376
    Fixed in
    • 10.0.22000.376
  • Microsoft Windows 10 Version 21H232-bit, ARM64
    Affected
    • < 10.0.19044.1415
    Fixed in
    • 10.0.19044.1415
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.19145
    Fixed in
    • 10.0.10240.19145
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.4825
    Fixed in
    • 10.0.14393.4825
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.4825
    Fixed in
    • 10.0.14393.4825
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.4825
    Fixed in
    • 10.0.14393.4825
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.25796
    Fixed in
    • 6.1.7601.25796
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.25796
    Fixed in
    • 6.1.7601.25796
  • Microsoft Windows 8.132-bit, x64, ARM64
    Affected
    • < 6.3.9600.20207
    Fixed in
    • 6.3.9600.20207
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.21309
    Fixed in
    • 6.0.6003.21309
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21309
    Fixed in
    • 6.0.6003.21309
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.25796
    Fixed in
    • 6.1.7601.25796
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.25796
    Fixed in
    • 6.1.7601.25796
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23540
    • < 6.2.9200.23545
    Fixed in
    • 6.2.9200.23540
    • 6.2.9200.23545
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23540
    • < 6.2.9200.23545
    Fixed in
    • 6.2.9200.23540
    • 6.2.9200.23545
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20207
    Fixed in
    • 6.3.9600.20207
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20207
    Fixed in
    • 6.3.9600.20207

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.2366
    • Microsoft Windows Server 2019: 10.0.17763.2366
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.2366
    • Microsoft Windows 10 Version 1909: 10.0.18363.1977
    • Microsoft Windows 10 Version 21H1: 10.0.19043.1415
    • Microsoft Windows Server 2022: 10.0.20348.405
    Fixed versions for 21 more products are in the table above.
  • Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
  • CISA's deadline for US federal agencies: 2025-10-27 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to the fixed build listed for its Windows version, or later.
  2. Prioritize patching, since CISA lists the flaw as known exploited with ransomware use.
  3. Follow the Microsoft advisory and CISA's required action; discontinue use of the product if mitigations are unavailable.
  4. Limit local and interactive access to systems and enforce least privilege for user accounts.
  5. Check unpatched or recently patched systems for signs of compromise.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Questions about CVE-2021-43226

Is CVE-2021-43226 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-10-06 and reports known ransomware use. US federal agencies must address it by 2025-10-27.
Can it be exploited remotely?
No. The attack vector is local, and the attacker needs low privileges on the system. No user interaction is required.
Which update fixes it?
Each affected Windows version has a fixed build in the CVE record, for example 10.0.17763.2366 for Windows 10 Version 1809 and Windows Server 2019, or 10.0.22000.376 for Windows 11 version 21H2.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.