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

CVE-2021-36955: Microsoft Windows Common Log File System (CLFS) Driver Privilege Escalation

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
4.1%
higher than 90.9% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2021-11-17
Automatable (CISA SSVC)
no
technical impact: total

CVE-2021-36955 explained

CVE-2021-36955 is a privilege escalation vulnerability in the Microsoft Windows Common Log File System (CLFS) driver. It affects many Windows client and server versions. CISA lists it as known exploited and notes known use in ransomware campaigns, so unpatched systems face real risk.

Impact

An attacker who can already run code with low privileges on a system can escalate privileges locally, without user interaction. Successful exploitation gives high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA does not consider it automatable, so each attack needs manual steps. Attackers are known to exploit it, including in ransomware activity.

Who is affected

The CVE record lists Windows 10 Version 1507 before 10.0.10240.19060, 1607 before 10.0.14393.4651, 1809 before 10.0.17763.2183, 1909 before 10.0.18363.1801, 2004 before 10.0.19041.1237, 20H2 before 10.0.19042.1237 and 21H1 before 10.0.19043.1237. Windows 7, Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1 (including Server Core) are affected before 6.1.7601.25712. Windows 8.1 is affected before 6.3.9600.20120. Each listed version is the fix. 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 (CLFS) driver contains an unspecified vulnerability that allows for privilege escalation.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

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

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.19060
    Fixed in
    • 10.0.10240.19060
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.4651
    Fixed in
    • 10.0.14393.4651
  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.2183
    Fixed in
    • 10.0.17763.2183
  • Microsoft Windows 10 Version 190932-bit, ARM64, x64
    Affected
    • < 10.0.18363.1801
    Fixed in
    • 10.0.18363.1801
  • Microsoft Windows 10 Version 200432-bit, ARM64, x64
    Affected
    • < 10.0.19041.1237
    Fixed in
    • 10.0.19041.1237
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1237
    Fixed in
    • 10.0.19042.1237
  • Microsoft Windows 10 Version 21H132-bit, ARM64, x64
    Affected
    • < 10.0.19043.1237
    Fixed in
    • 10.0.19043.1237
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.25712
    Fixed in
    • 6.1.7601.25712
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.25712
    Fixed in
    • 6.1.7601.25712
  • Microsoft Windows 8.132-bit, ARM64, x64
    Affected
    • < 6.3.9600.20120
    Fixed in
    • 6.3.9600.20120
Show 15 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.25712
    Fixed in
    • 6.1.7601.25712
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.25712
    Fixed in
    • 6.1.7601.25712
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.21218
    Fixed in
    • 6.0.6003.21218
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21218
    Fixed in
    • 6.0.6003.21218
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23462
    Fixed in
    • 6.2.9200.23462
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23462
    Fixed in
    • 6.2.9200.23462
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20120
    Fixed in
    • 6.3.9600.20120
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20120
    Fixed in
    • 6.3.9600.20120
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.4651
    Fixed in
    • 10.0.14393.4651
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.4651
    Fixed in
    • 10.0.14393.4651
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.2183
    Fixed in
    • 10.0.17763.2183
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.2183
    Fixed in
    • 10.0.17763.2183
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.230
    Fixed in
    • 10.0.20348.230
  • Microsoft Windows Server version 2004x64
    Affected
    • < 10.0.19041.1237
    Fixed in
    • 10.0.19041.1237
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1237
    Fixed in
    • 10.0.19042.1237

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.19060
    • Microsoft Windows 10 Version 1607: 10.0.14393.4651
    • Microsoft Windows 10 Version 1809: 10.0.17763.2183
    • Microsoft Windows 10 Version 1909: 10.0.18363.1801
    • Microsoft Windows 10 Version 2004: 10.0.19041.1237
    • Microsoft Windows 10 Version 20H2: 10.0.19042.1237
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2021-36955
  • CISA's deadline for US federal agencies: 2021-11-17 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply Microsoft's security update so each system reaches at least the fixed build listed for its Windows version.
  2. Prioritize patching, since CISA lists this flaw as known exploited and used in ransomware.
  3. Follow the Microsoft advisory for update details and product-specific instructions.
  4. Limit local and interactive access to systems to trusted users and keep user privileges to a minimum.
  5. Check unpatched or recently patched systems for signs of compromise, such as unexpected privileged accounts or processes.

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-36955

Can this be exploited remotely?
No. The attack vector is local. An attacker needs low-privileged access to the system first, then uses the flaw to gain higher privileges.
Is this vulnerability exploited in the wild?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03 and notes known ransomware use. The required action is to apply updates per vendor instructions.
Which build fixes Windows 10 Version 21H1?
The CVE record names 10.0.19043.1237 as the fixed version for Windows 10 Version 21H1. Earlier builds are affected.

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-22. Always confirm with the vendor's or distribution's advisory before patching.