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

CVE-2021-1675: Microsoft Windows Print Spooler Remote Code Execution

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)
85%
higher than 99.7% 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-1675 explained

CVE-2021-1675 is a remote code execution vulnerability in the Microsoft Windows Print Spooler. It affects many Windows 10 and Windows Server releases. CISA lists it as known to be exploited, including in ransomware campaigns, which makes patching a priority.

Impact

An attacker who exploits this flaw can execute code and fully compromise confidentiality, integrity and availability of the affected system. The CVSS vector rates it as local, low complexity, needing no privileges but requiring user interaction. CISA rates the technical impact as total, meaning total control of the affected component. CISA rates it as not automatable. It is known to be exploited, including for ransomware.

Who is affected

The CVE record lists Windows 10 Versions 1507, 1607, 1809, 1909, 2004, 20H2 and 21H1, and Windows Server 2016, 2019 (including Server Core), version 2004 and version 20H2. Fixed builds include 10.0.17763.1999 (1809/Server 2019), 10.0.18363.1621 (1909), 10.0.19041.1052 (2004), 10.0.19042.1052 (20H2), 10.0.19043.1052 (21H1), 10.0.10240.18967 (1507) and 10.0.14393.4467 (1607/Server 2016). 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 Print Spooler contains an unspecified vulnerability that allows for remote code execution.

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 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.1999
    Fixed in
    • 10.0.17763.1999
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.1999
    Fixed in
    • 10.0.17763.1999
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.1999
    Fixed in
    • 10.0.17763.1999
  • Microsoft Windows 10 Version 190932-bit, x64, ARM64
    Affected
    • < 10.0.18363.1621
    Fixed in
    • 10.0.18363.1621
  • Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit
    Affected
    • < 10.0.19043.1052
    Fixed in
    • 10.0.19043.1052
  • Microsoft Windows 10 Version 200432-bit, ARM64, x64
    Affected
    • < 10.0.19041.1052
    Fixed in
    • 10.0.19041.1052
  • Microsoft Windows Server version 2004x64
    Affected
    • < 10.0.19041.1052
    Fixed in
    • 10.0.19041.1052
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1052
    Fixed in
    • 10.0.19042.1052
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1052
    Fixed in
    • 10.0.19042.1052
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.18967
    Fixed in
    • 10.0.10240.18967
Show 14 more products
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.4467
    Fixed in
    • 10.0.14393.4467
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.4467
    Fixed in
    • 10.0.14393.4467
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.4467
    Fixed in
    • 10.0.14393.4467
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.25632
    Fixed in
    • 6.1.7601.25632
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.25632
    Fixed in
    • 6.1.7601.25632
  • Microsoft Windows 8.132-bit, x64, ARM64
    Affected
    • < 6.3.9600.20044
    • < 6.3.9600.20045
    Fixed in
    • 6.3.9600.20044
    • 6.3.9600.20045
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.21137
    Fixed in
    • 6.0.6003.21137
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21137
    Fixed in
    • 6.0.6003.21137
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.25632
    Fixed in
    • 6.1.7601.25632
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.25632
    Fixed in
    • 6.1.7601.25632
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23372
    Fixed in
    • 6.2.9200.23372
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23372
    Fixed in
    • 6.2.9200.23372
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20044
    • < 6.3.9600.20045
    Fixed in
    • 6.3.9600.20044
    • 6.3.9600.20045
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20044
    • < 6.3.9600.20045
    Fixed in
    • 6.3.9600.20044
    • 6.3.9600.20045

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.1999
    • Microsoft Windows Server 2019: 10.0.17763.1999
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.1999
    • Microsoft Windows 10 Version 1909: 10.0.18363.1621
    • Microsoft Windows 10 Version 21H1: 10.0.19043.1052
    • Microsoft Windows 10 Version 2004: 10.0.19041.1052
    Fixed versions for 18 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: 2021-11-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 vendor advisory for any additional guidance or mitigations for the Print Spooler service.
  3. Inventory all Windows systems and confirm their build numbers against the fixed versions.
  4. Check systems for signs of compromise, given known exploitation and ransomware use.
  5. Replace or upgrade any Windows versions that cannot receive the updates.

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

Questions about CVE-2021-1675

Is CVE-2021-1675 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03 and notes known use in ransomware campaigns. US federal agencies had to apply updates by 2021-11-17.
What does CISA require?
CISA's required action is to apply updates per vendor instructions.
How do I know if a system is fixed?
Compare the OS build with the fixed version for its release, for example 10.0.17763.1999 for Windows 10 Version 1809 and Windows Server 2019, or 10.0.14393.4467 for Windows 10 Version 1607 and Windows Server 2016.

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.