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

CVE-2022-41073: Microsoft Windows Print Spooler Privilege Escalation

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

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
2.6%
higher than 85.8% of all CVEs
Added to CISA KEV
2022-11-08
US federal due date 2022-12-09
Automatable (CISA SSVC)
no
technical impact: total

CVE-2022-41073 explained

CVE-2022-41073 is an out-of-bounds write vulnerability in the Microsoft Windows Print Spooler that lets an attacker gain SYSTEM-level privileges. It affects many Windows client versions. CISA lists it as known exploited, including use in ransomware campaigns, so unpatched systems are at real risk.

Impact

An attacker who already has low-privileged local access can elevate to SYSTEM without any user interaction. This gives total control of the affected system, with high impact on confidentiality, integrity and availability. CISA rates it as not automatable, so exploitation needs a foothold on each target. Attackers are known to exploit it, and CISA reports known ransomware use.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 20H2, 21H1, 21H2 and 22H2, Windows 11 versions 21H2 and 22H2, Windows 7, Windows 7 Service Pack 1, and Windows 8.1. Fixed builds include 10.0.10240.19567, 10.0.14393.5501, 10.0.17763.3650, 10.0.19042.2251, 10.0.19043.2251, 10.0.19044.2251, 10.0.19045.2251, 10.0.22000.1219, 10.0.22621.819, 6.1.7601.26221 and 6.3.9600.20671. The page lists 13 further products.

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 an attacker to gain SYSTEM-level privileges.

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.19567
    Fixed in
    • 10.0.10240.19567
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.5501
    Fixed in
    • 10.0.14393.5501
  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.3650
    Fixed in
    • 10.0.17763.3650
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.2251
    Fixed in
    • 10.0.19042.2251
  • Microsoft Windows 10 Version 21H132-bit, ARM64, x64
    Affected
    • < 10.0.19043.2251
    Fixed in
    • 10.0.19043.2251
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.2251
    Fixed in
    • 10.0.19044.2251
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.2251
    Fixed in
    • 10.0.19045.2251
  • Microsoft Windows 11 version 21H2ARM64, x64
    Affected
    • < 10.0.22000.1219
    Fixed in
    • 10.0.22000.1219
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.819
    Fixed in
    • 10.0.22621.819
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.26221
    Fixed in
    • 6.1.7601.26221
Show 15 more products
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.26221
    Fixed in
    • 6.1.7601.26221
  • Microsoft Windows 8.132-bit, ARM64, x64
    Affected
    • < 6.3.9600.20671
    Fixed in
    • 6.3.9600.20671
  • Microsoft Windows Server 2008 Service Pack 2x64, 32-bit
    Affected
    • < 6.0.6003.21768
    Fixed in
    • 6.0.6003.21768
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.26221
    Fixed in
    • 6.1.7601.26221
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.26221
    Fixed in
    • 6.1.7601.26221
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21768
    Fixed in
    • 6.0.6003.21768
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23968
    Fixed in
    • 6.2.9200.23968
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23968
    Fixed in
    • 6.2.9200.23968
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20671
    Fixed in
    • 6.3.9600.20671
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20671
    Fixed in
    • 6.3.9600.20671
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.5501
    Fixed in
    • 10.0.14393.5501
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.5501
    Fixed in
    • 10.0.14393.5501
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.3650
    Fixed in
    • 10.0.17763.3650
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.3650
    Fixed in
    • 10.0.17763.3650
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.1249
    Fixed in
    • 10.0.20348.1249

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.19567
    • Microsoft Windows 10 Version 1607: 10.0.14393.5501
    • Microsoft Windows 10 Version 1809: 10.0.17763.3650
    • Microsoft Windows 10 Version 20H2: 10.0.19042.2251
    • Microsoft Windows 10 Version 21H1: 10.0.19043.2251
    • Microsoft Windows 10 Version 21H2: 10.0.19044.2251
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41073
  • CISA's deadline for US federal agencies: 2022-12-09 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply the Microsoft security update that brings each system to the fixed build listed for its Windows version.
  2. Prioritize patching, since CISA lists this vulnerability as known exploited with ransomware use.
  3. Follow the Microsoft advisory for the additional affected products listed on this page.
  4. Limit local and low-privileged access to systems, and review accounts that can log on interactively.
  5. Check systems for signs of compromise, such as unexpected SYSTEM-level processes or new privileged accounts.

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-787 Out-of-bounds Write

Questions about CVE-2022-41073

Can this be exploited remotely?
The CVSS vector rates the attack vector as local. An attacker needs low-privileged access to the system first, then can gain SYSTEM-level privileges without user interaction.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-11-08 and reports known ransomware use. The US federal due date was 2022-12-09.
What does CISA require?
CISA's required action is to apply updates per vendor instructions.

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.