Skip to content
vulnerability

CVE-2021-43226

7.8
High
KEV · Exploited in wildEPSS 3%Patch available

Windows Common Log File System Driver Elevation of Privilege Vulnerability

exploited
Yes, in CISA KEV since 6 Oct 2025fix by 27 Oct 2025 (CISA deadline for US federal agencies)known use in ransomware campaignsunvetted proof-of-concept code on github
fix
Patch available see the advisory in the references
likelihood
EPSS 3.3%
Published 15 Dec 2021Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
surface unknownruntimeWAF can block: noAV · local

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-2021-43226 being exploited?

Yes. CVE-2021-43226 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-2021-43226?

CVE-2021-43226 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-2021-43226?

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

What does CVE-2021-43226 affect?

CVE-2021-43226 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_1909, and 15 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_1909microsoft:windows_10_2004microsoft:windows_10_20h2microsoft:windows_10_21h1microsoft:windows_10_21h2microsoft:windows_11_21h2microsoft:windows_7microsoft:windows_8.1microsoft:windows_rt_8.1microsoft:windows_server_2004microsoft:windows_server_2008microsoft:windows_server_2012microsoft:windows_server_2016microsoft:windows_server_2019microsoft:windows_server_2022microsoft:windows_server_20h2
affected versions
Microsoft Windows 10 Version 1507
  • affected>= 10.0.0 and < 10.0.10240.19145
Microsoft Windows 10 Version 1607
  • affected>= 10.0.0 and < 10.0.14393.4825
Microsoft Windows 10 Version 1809
  • affected>= 10.0.0 and < 10.0.17763.2366
Microsoft Windows 10 Version 1909
  • affected>= 10.0.0 and < 10.0.18363.1977
Microsoft Windows 10 Version 2004
  • affected>= 10.0.0 and < 10.0.19041.1415
Microsoft Windows 10 Version 20H2
  • affected>= 10.0.0 and < 10.0.19042.1415
Microsoft Windows 10 Version 21H1
  • affected>= 10.0.0 and < 10.0.19043.1415
Microsoft Windows 10 Version 21H2
  • affected>= 10.0.0 and < 10.0.19044.1415
Microsoft Windows 11 version 21H2
  • affected>= 10.0.0 and < 10.0.22000.376
Microsoft Windows 7
  • affected>= 6.1.0 and < 6.1.7601.25796
Microsoft Windows 7 Service Pack 1
  • affected>= 6.1.0 and < 6.1.7601.25796
Microsoft Windows 8.1
  • affected>= 6.3.0 and < 6.3.9600.20207
Microsoft Windows Server 2008 R2 Service Pack 1
  • affected>= 6.1.0 and < 6.1.7601.25796
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
  • affected>= 6.0.0 and < 6.1.7601.25796
Microsoft Windows Server 2008 Service Pack 2
  • affected>= 6.0.0 and < 6.0.6003.21309
Microsoft Windows Server 2008 Service Pack 2
  • affected>= 6.0.0 and < 6.0.6003.21309
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)
  • affected>= 6.0.0 and < 6.0.6003.21309
Microsoft Windows Server 2012
  • affected>= 6.2.0 and < 6.2.9200.23545
  • affected>= 6.2.0 and < 6.2.9200.23540
Microsoft Windows Server 2012 R2
  • affected>= 6.3.0 and < 6.3.9600.20207
Microsoft Windows Server 2012 R2 (Server Core installation)
  • affected>= 6.3.0 and < 6.3.9600.20207
Microsoft Windows Server 2012 (Server Core installation)
  • affected>= 6.2.0 and < 6.2.9200.23545
  • affected>= 6.2.0 and < 6.2.9200.23540
Microsoft Windows Server 2016
  • affected>= 10.0.0 and < 10.0.14393.4825
Microsoft Windows Server 2016 (Server Core installation)
  • affected>= 10.0.0 and < 10.0.14393.4825
Microsoft Windows Server 2019
  • affected>= 10.0.0 and < 10.0.17763.2366
Microsoft Windows Server 2019 (Server Core installation)
  • affected>= 10.0.0 and < 10.0.17763.2366
Microsoft Windows Server 2022
  • affected>= 10.0.0 and < 10.0.20348.405
Microsoft Windows Server version 2004
  • affected>= 10.0.0 and < 10.0.19041.1415
Microsoft Windows Server version 20H2
  • affected>= 10.0.0 and < 10.0.19042.1415

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

Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept

GitHub proofs of concept

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 16 Dec 2021 (SSVC 2.0.3).

timeline

  1. 15 Dec 2021Published
  2. 16 Dec 2021CISA SSVC assessment: exploitation active · same day later
  3. 30 Oct 2023First proof-of-concept repository on GitHub (unvetted) · 683 days (about 2 years) later
  4. 6 Oct 2025Added to CISA KEV (exploited in the wild) · 707 days (about 2 years) later
  5. 27 Oct 2025CISA remediation due date (US federal agencies) · 21 days later
  6. 22 Aug 2026CVE record last updated · 299 days (about 10 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 73 days (about 2 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: 2 links

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved