Skip to content
Server Security Center
KEVhigh7.8

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

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

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
18%
higher than 97.3% of all CVEs
Added to CISA KEV
2022-04-19
US federal due date 2022-05-10
Automatable (CISA SSVC)
no
technical impact: total

CVE-2022-22718 explained

CVE-2022-22718 is an unspecified privilege escalation vulnerability in the Microsoft Windows Print Spooler. It affects many Windows 10, Windows 11 and Windows Server releases. CISA lists it as known to be exploited, so unpatched systems where low-privileged users or malware can run code are at real risk of full compromise.

Impact

An attacker who already has low-privileged local access can escalate privileges without user interaction. Successful exploitation can fully compromise confidentiality, integrity and availability of the affected system. CISA rates the technical impact as total, meaning total control of the affected component. It rates the flaw as not automatable, so exploitation is not expected at scale without manual steps. Attackers are known to use this vulnerability; ransomware use is listed as unknown.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 1909, 20H2, 21H1 and 21H2, Windows 11 version 21H2, Windows Server 2019 (including Server Core), Windows Server 2022 and Windows Server version 20H2. Example fixed builds: 10.0.17763.2565 (1809/Server 2019), 10.0.19044.1526 (10 21H2), 10.0.22000.493 (11 21H2), 10.0.20348.524 (Server 2022), 10.0.14393.4946 (1607), 10.0.10240.19204 (1507). 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 which allow 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 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.2565
    Fixed in
    • 10.0.17763.2565
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.2565
    Fixed in
    • 10.0.17763.2565
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.2565
    Fixed in
    • 10.0.17763.2565
  • Microsoft Windows 10 Version 190932-bit, x64, ARM64
    Affected
    • < 10.0.18363.2094
    Fixed in
    • 10.0.18363.2094
  • Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit
    Affected
    • < 10.0.19043.1526
    Fixed in
    • 10.0.19043.1526
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.524
    Fixed in
    • 10.0.20348.524
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1526
    Fixed in
    • 10.0.19042.1526
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1526
    Fixed in
    • 10.0.19042.1526
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.493
    Fixed in
    • 10.0.22000.493
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.1526
    Fixed in
    • 10.0.19044.1526
Show 15 more products
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.19204
    Fixed in
    • 10.0.10240.19204
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.4946
    Fixed in
    • 10.0.14393.4946
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.4946
    Fixed in
    • 10.0.14393.4946
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.4946
    Fixed in
    • 10.0.14393.4946
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.25860
    Fixed in
    • 6.1.7601.25860
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.25860
    Fixed in
    • 6.1.7601.25860
  • Microsoft Windows 8.132-bit, x64, ARM64
    Affected
    • < 6.3.9600.20269
    Fixed in
    • 6.3.9600.20269
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.21374
    Fixed in
    • 6.0.6003.21374
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21374
    Fixed in
    • 6.0.6003.21374
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.25860
    Fixed in
    • 6.1.7601.25860
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.25860
    Fixed in
    • 6.1.7601.25860
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23605
    Fixed in
    • 6.2.9200.23605
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23605
    Fixed in
    • 6.2.9200.23605
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20269
    Fixed in
    • 6.3.9600.20269
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20269
    Fixed in
    • 6.3.9600.20269

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.2565
    • Microsoft Windows Server 2019: 10.0.17763.2565
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.2565
    • Microsoft Windows 10 Version 1909: 10.0.18363.2094
    • Microsoft Windows 10 Version 21H1: 10.0.19043.1526
    • Microsoft Windows Server 2022: 10.0.20348.524
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-22718
  • CISA's deadline for US federal agencies: 2022-05-10 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security updates that bring each system to the fixed build listed for its Windows version, for example 10.0.17763.2565 or 10.0.22000.493.
  2. Prioritize servers and multi-user systems where untrusted or low-privileged users can sign in.
  3. Follow the Microsoft advisory for the full product list, including the further products shown on this page.
  4. Verify installed build numbers across the fleet to confirm that updates applied successfully.
  5. Review systems for signs of compromise, such as unexpected privileged accounts or services, since the flaw is known to be exploited.

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-2022-22718

Can this be exploited remotely?
The CVSS vector lists the attack vector as local. An attacker needs low-privileged access to the system first, then can escalate to higher privileges. No user interaction is required.
Is this vulnerability being exploited?
Yes. CISA added CVE-2022-22718 to its Known Exploited Vulnerabilities catalog on 2022-04-19, with a US federal due date of 2022-05-10. Whether it is used in ransomware campaigns is listed as unknown.
What does CISA require?
CISA's required action is to apply updates per vendor instructions. Install the Microsoft updates that bring each affected Windows version to its fixed build.

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.