Skip to content
Server Security Center
KEVmedium5.5 Used in ransomware campaigns

CVE-2021-41379: Microsoft Windows Installer Privilege Escalation

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

CVSS v3.1 (CVE record)
5.5
medium
EPSS (exploit probability, 30 days)
19%
higher than 97.4% of all CVEs
Added to CISA KEV
2022-03-03
US federal due date 2022-03-17
Automatable (CISA SSVC)
no
technical impact: total

CVE-2021-41379 explained

CVE-2021-41379 is a privilege escalation vulnerability in Microsoft Windows Installer, affecting many Windows client and server versions. The weakness is improper link resolution before file access. CISA lists it as known exploited, including in ransomware campaigns, so unpatched systems are at real risk.

Impact

A local attacker who already has low-privileged access can escalate privileges without user interaction. The CVSS vector rates availability impact as high, while CISA's SSVC assessment rates the technical impact as total, meaning total control of the affected component. CISA rates it as not automatable. CISA reports known exploitation, including use in ransomware campaigns.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 1909, 2004, 20H2 and 21H1, Windows 11 version 21H2, Windows 7, Windows 7 Service Pack 1, Windows 8.1 and Windows Server 2008 R2 Service Pack 1. Fixed builds include 10.0.10240.19119, 10.0.14393.4770, 10.0.17763.2300, 10.0.18363.1916, 10.0.19041.1348, 10.0.19042.1348, 10.0.19043.1348, 10.0.22000.318, 6.3.9600.20174 and 6.1.7601.25769. The page lists further products.

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

Official description

Microsoft Windows Installer 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.19119
    Fixed in
    • 10.0.10240.19119
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.4770
    Fixed in
    • 10.0.14393.4770
  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.2300
    Fixed in
    • 10.0.17763.2300
  • Microsoft Windows 10 Version 190932-bit, ARM64, x64
    Affected
    • < 10.0.18363.1916
    Fixed in
    • 10.0.18363.1916
  • Microsoft Windows 10 Version 200432-bit, ARM64, x64
    Affected
    • < 10.0.19041.1348
    Fixed in
    • 10.0.19041.1348
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1348
    Fixed in
    • 10.0.19042.1348
  • Microsoft Windows 10 Version 21H132-bit, ARM64, x64
    Affected
    • < 10.0.19043.1348
    Fixed in
    • 10.0.19043.1348
  • Microsoft Windows 11 version 21H2ARM64, x64
    Affected
    • < 10.0.22000.318
    Fixed in
    • 10.0.22000.318
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.25769
    Fixed in
    • 6.1.7601.25769
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.25769
    Fixed in
    • 6.1.7601.25769
Show 16 more products
  • Microsoft Windows 8.132-bit, ARM64, x64
    Affected
    • < 6.3.9600.20174
    Fixed in
    • 6.3.9600.20174
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.25769
    Fixed in
    • 6.1.7601.25769
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.25769
    Fixed in
    • 6.1.7601.25769
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.21282
    Fixed in
    • 6.0.6003.21282
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21282
    Fixed in
    • 6.0.6003.21282
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23517
    Fixed in
    • 6.2.9200.23517
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23517
    Fixed in
    • 6.2.9200.23517
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20174
    Fixed in
    • 6.3.9600.20174
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20174
    Fixed in
    • 6.3.9600.20174
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.4770
    Fixed in
    • 10.0.14393.4770
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.4770
    Fixed in
    • 10.0.14393.4770
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.2300
    Fixed in
    • 10.0.17763.2300
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.2300
    Fixed in
    • 10.0.17763.2300
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.350
    Fixed in
    • 10.0.20348.350
  • Microsoft Windows Server version 2004x64
    Affected
    • < 10.0.19041.1348
    Fixed in
    • 10.0.19041.1348
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1348
    Fixed in
    • 10.0.19042.1348

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.19119
    • Microsoft Windows 10 Version 1607: 10.0.14393.4770
    • Microsoft Windows 10 Version 1809: 10.0.17763.2300
    • Microsoft Windows 10 Version 1909: 10.0.18363.1916
    • Microsoft Windows 10 Version 2004: 10.0.19041.1348
    • Microsoft Windows 10 Version 20H2: 10.0.19042.1348
    Fixed versions for 20 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2021-41379
  • CISA's deadline for US federal agencies: 2022-03-17 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply Microsoft's security updates so each system reaches at least the fixed build listed for its Windows version.
  2. Follow the Microsoft vendor advisory for the update matching each affected product, including Windows Server 2008 R2 Service Pack 1.
  3. Limit local logon rights and low-privileged accounts on systems that cannot be patched promptly.
  4. Check systems for signs of compromise, given CISA's report of known ransomware use.
  5. Verify patch status across the fleet using the build numbers in the CVE record.

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

Weakness: CWE-59 Improper Link Resolution Before File Access ('Link Following')

Questions about CVE-2021-41379

Is CVE-2021-41379 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-03 and reports known ransomware use. The US federal due date was 2022-03-17.
Can it be exploited remotely?
The CVSS vector lists a local attack vector. An attacker needs low-privileged access to the system, and no user interaction is required.
What does CISA require?
CISA's required action is to apply updates per vendor instructions. Update each affected Windows version to the fixed build listed in the CVE record.

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.