CriticalCVE-2022-22718

    Windows Print Spooler Elevation of Privilege Vulnerability (CVE-2022-22718)

    Published In CISA KEV since Sources: CVE.org

    What is affected, what to do

    Windows Print Spooler Elevation of Privilege Vulnerability

    The vulnerability is being actively exploited; treat it as a priority. Update Microsoft Windows 10 Version 1809 to version 10.0.17763.2565, Microsoft Windows Server 2019 to version 10.0.17763.2565, Microsoft Windows Server 2019 (Server Core installation) to version 10.0.17763.2565. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Microsoft Windows 10 Version 1809 lt 10.0.17763.0..10.0.17763.2565
    • Microsoft Windows Server 2019 lt 10.0.17763.0..10.0.17763.2565
    • Microsoft Windows Server 2019 (Server Core installation) lt 10.0.17763.0..10.0.17763.2565
    • Microsoft Windows 10 Version 1909 lt 10.0.0..10.0.18363.2094
    • Microsoft Windows 10 Version 21H1 lt 10.0.0..10.0.19043.1526
    • Microsoft Windows Server 2022 lt 10.0.20348.0..10.0.20348.524
    • Microsoft Windows 10 Version 20H2 lt 10.0.0..10.0.19042.1526
    • Microsoft Windows Server version 20H2 lt 10.0.0..10.0.19042.1526
    • Microsoft Windows 11 version 21H2 lt 10.0.0..10.0.22000.493
    • Microsoft Windows 10 Version 21H2 lt 10.0.19043.0..10.0.19044.1526
    • Microsoft Windows 10 Version 1507 lt 10.0.10240.0..10.0.10240.19204
    • Microsoft Windows 10 Version 1607 lt 10.0.14393.0..10.0.14393.4946
    • Microsoft Windows Server 2016 lt 10.0.14393.0..10.0.14393.4946
    • Microsoft Windows Server 2016 (Server Core installation) lt 10.0.14393.0..10.0.14393.4946
    • Microsoft Windows 7 lt 6.1.0..6.1.7601.25860
    • Microsoft Windows 7 Service Pack 1 lt 6.1.0..6.1.7601.25860
    • Microsoft Windows 8.1 lt 6.3.0..6.3.9600.20269
    • Microsoft Windows Server 2008 Service Pack 2 lt 6.0.6003.0..6.0.6003.21374
    • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) lt 6.0.6003.0..6.0.6003.21374
    • Microsoft Windows Server 2008 R2 Service Pack 1 lt 6.1.7601.0..6.1.7601.25860
    • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) lt 6.1.7601.0..6.1.7601.25860
    • Microsoft Windows Server 2012 lt 6.2.9200.0..6.2.9200.23605
    • Microsoft Windows Server 2012 (Server Core installation) lt 6.2.9200.0..6.2.9200.23605
    • Microsoft Windows Server 2012 R2 lt 6.3.9600.0..6.3.9600.20269
    • Microsoft Windows Server 2012 R2 (Server Core installation) lt 6.3.9600.0..6.3.9600.20269
    Fixed in
    • 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
    • Microsoft Windows 10 Version 20H2 10.0.19042.1526
    • Microsoft Windows Server version 20H2 10.0.19042.1526
    • Microsoft Windows 11 version 21H2 10.0.22000.493
    • Microsoft Windows 10 Version 21H2 10.0.19044.1526
    • Microsoft Windows 10 Version 1507 10.0.10240.19204
    • Microsoft Windows 10 Version 1607 10.0.14393.4946
    • Microsoft Windows Server 2016 10.0.14393.4946
    • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.4946
    • Microsoft Windows 7 6.1.7601.25860
    • Microsoft Windows 7 Service Pack 1 6.1.7601.25860
    • Microsoft Windows 8.1 6.3.9600.20269
    • Microsoft Windows Server 2008 Service Pack 2 6.0.6003.21374
    • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) 6.0.6003.21374
    • Microsoft Windows Server 2008 R2 Service Pack 1 6.1.7601.25860
    • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) 6.1.7601.25860
    • Microsoft Windows Server 2012 6.2.9200.23605
    • Microsoft Windows Server 2012 (Server Core installation) 6.2.9200.23605
    • Microsoft Windows Server 2012 R2 6.3.9600.20269
    • Microsoft Windows Server 2012 R2 (Server Core installation) 6.3.9600.20269

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org

    18.5 %

    EPSS score

    Elevated — model estimates 10-50% exploitation likelihood.

    Source: FIRST EPSS, percentile 97.2

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    215.05 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    18.5 %
    Elevated — model estimates 10-50% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    97.2
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 29 January 2025

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This is a textbook post-exploitation primitive: an attacker who already has a foothold as a regular user escalates to SYSTEM without user interaction, gaining full control over confidentiality, integrity and availability of the host — the springboard for credential dumping, EDR tampering and lateral movement. The Print Spooler has been a favoured target since PrintNightmare because it runs by default on almost every Windows system and public exploitation techniques are available; exploitation likelihood is very high, while CISA does not flag known ransomware use. The most exposed assets are multi-user environments (RDS/VDI), domain controllers with the spooler still running, and unpatched legacy clients. Score it high for any spooler-enabled system with multiple users or a Tier-0 role, medium for single-user clients with current EDR coverage — and treat a patch backlog of this age as a material finding in NIS2 risk management.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Verify patch level and deploy the February 2022 cumulative security update. Minimum fixed builds per the advisory: Windows 10 1507 → 10.0.10240.19204, 1607 → 10.0.14393.4946, 1809 → 10.0.17763.2565, 1909 → 10.0.18363.2094, 20H2 → 10.0.19042.1526, 21H1 → 10.0.19043.1526, 21H2 → 10.0.19044.1526, Windows 11 21H2 → 10.0.22000.493. Look up the per-build KB numbers in the Microsoft Security Update Guide. Query Intune/SCCM/Defender TVM for OSBuild values below these thresholds.
      • Check Windows Server separately: the context only lists client builds; server releases running Print Spooler (including Windows Server 2016/2019/2022) must be verified against the vendor advisory — look up the fixed version there.
      • Disable the Print Spooler service (Spooler) wherever printing is not required, starting with domain controllers, Tier-0 servers, jump hosts and hypervisor management: Stop-Service Spooler -Force; Set-Service Spooler -StartupType Disabled, or enforce via GPO.
      • Prioritise hosts with signs of prior compromise: exploitation requires low-privileged local access, so patch or isolate hosts with open EDR alerts, phishing hits, or shared multi-user roles (RDS, Citrix, VDI) first.
      • Enforce Point and Print hardening via GPO now: set RestrictDriverInstallationToAdministrators = 1 under HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PointAndPrint; ensure NoWarningNoElevationOnInstall and UpdatePromptSettings are not set to 1.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: allow clients to reach only authorised print servers over SMB (TCP 445) and RPC (TCP 135 plus dynamic RPC range). Block outbound SMB to the internet at the perimeter so drivers cannot be pulled from attacker-controlled print servers.
      • Configuration hardening (GPO): enable "Package Point and Print – Approved servers" listing internal print servers only; set "Point and Print Restrictions" to "Users can only point and print to these servers". Disable inbound remote printing on clients with "Allow Print Spooler to accept client connections = Disabled".
      • Endpoint hardening / application control: WDAC or AppLocker DLL rules blocking unsigned or unapproved DLLs loading from C:\Windows\System32\spool\drivers\; switch Defender ASR rules to block mode (notably blocking abuse of exploited vulnerable signed drivers).
      • IAM / least privilege: remove standing local admin rights (LAPS for local admin accounts), strictly separate standard users on multi-user systems; audit write permissions on spool\drivers and spool\PRINTERS.
      • Unpatchable legacy systems (e.g. out-of-support Windows 10 1507/1607): disable the spooler or move them into a dedicated VLAN without lateral SMB/RPC paths until migration is complete.

    3. Runbook step 3

      Detection rules

      • Sysmon EID 1 / EDR process ancestry: spoolsv.exe spawning cmd.exe, powershell.exe, rundll32.exe, conhost.exe or unknown binaries. KQL: DeviceProcessEvents | where InitiatingProcessFileName =~ "spoolsv.exe" and FileName in~ ("cmd.exe","powershell.exe","rundll32.exe").
      • Sysmon EID 7 / EID 11: spoolsv.exe loading DLLs with Signed=false, and new files in C:\Windows\System32\spool\drivers\x64\3\ or ...\spool\drivers\W32X86\ not tied to a patch or driver rollout. Sigma shape: Image|endswith: '\spoolsv.exe' AND ImageLoaded|contains: '\spool\drivers\' AND Signed: 'false'.
      • Microsoft-Windows-PrintService/Operational and /Admin: EID 316 (printer driver added), EID 808 (failed to load plug-in module) and EID 307 on systems without legitimate printing. The Operational channel is off by default — enable it via GPO and forward to the SIEM.
      • Registry monitoring (Sysmon EID 13): writes under HKLM\SYSTEM\CurrentControlSet\Control\Print\Environments\*\Drivers\ and HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PointAndPrint from non-admin contexts or unexpected processes.
      • Follow-on privilege escalation: correlate Windows Security EID 4688 showing SYSTEM-level processes traced back to a standard-user logon, and EID 4720/4732 (new local account / added to Administrators) shortly after spooler anomalies.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Windows Print Spooler Elevation of Privilege Vulnerability

    Source: NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    MicrosoftWindows 10 Version 1507
    • 10.0.10240.0 – < 10.0.10240.19204
    • 10.0.10240.19204
    MicrosoftWindows 10 Version 1607
    • 10.0.14393.0 – < 10.0.14393.4946
    • 10.0.14393.4946
    MicrosoftWindows 10 Version 1809
    • 10.0.17763.0 – < 10.0.17763.2565
    • 10.0.17763.2565
    MicrosoftWindows 10 Version 1909
    • 10.0.0 – < 10.0.18363.2094
    • 10.0.18363.2094
    MicrosoftWindows 10 Version 20H2
    • 10.0.0 – < 10.0.19042.1526
    • 10.0.19042.1526
    MicrosoftWindows 10 Version 21H1
    • 10.0.0 – < 10.0.19043.1526
    • 10.0.19043.1526
    MicrosoftWindows 10 Version 21H2
    • 10.0.19043.0 – < 10.0.19044.1526
    • 10.0.19044.1526
    MicrosoftWindows 11 version 21H2
    • 10.0.0 – < 10.0.22000.493
    • 10.0.22000.493
    MicrosoftWindows 7
    • 6.1.0 – < 6.1.7601.25860
    • 6.1.7601.25860
    MicrosoftWindows 7 Service Pack 1
    • 6.1.0 – < 6.1.7601.25860
    • 6.1.7601.25860
    MicrosoftWindows 8.1
    • 6.3.0 – < 6.3.9600.20269
    • 6.3.9600.20269
    MicrosoftWindows Server 2008 R2 Service Pack 1
    • 6.1.7601.0 – < 6.1.7601.25860
    • 6.1.7601.25860
    MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)
    • 6.1.7601.0 – < 6.1.7601.25860
    • 6.1.7601.25860
    MicrosoftWindows Server 2008 Service Pack 2
    • 6.0.6003.0 – < 6.0.6003.21374
    • 6.0.6003.21374
    MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)
    • 6.0.6003.0 – < 6.0.6003.21374
    • 6.0.6003.21374
    MicrosoftWindows Server 2012
    • 6.2.9200.0 – < 6.2.9200.23605
    • 6.2.9200.23605
    MicrosoftWindows Server 2012 (Server Core installation)
    • 6.2.9200.0 – < 6.2.9200.23605
    • 6.2.9200.23605
    MicrosoftWindows Server 2012 R2
    • 6.3.9600.0 – < 6.3.9600.20269
    • 6.3.9600.20269
    MicrosoftWindows Server 2012 R2 (Server Core installation)
    • 6.3.9600.0 – < 6.3.9600.20269
    • 6.3.9600.20269
    MicrosoftWindows Server 2016
    • 10.0.14393.0 – < 10.0.14393.4946
    • 10.0.14393.4946
    MicrosoftWindows Server 2016 (Server Core installation)
    • 10.0.14393.0 – < 10.0.14393.4946
    • 10.0.14393.4946
    MicrosoftWindows Server 2019
    • 10.0.17763.0 – < 10.0.17763.2565
    • 10.0.17763.2565
    MicrosoftWindows Server 2019 (Server Core installation)
    • 10.0.17763.0 – < 10.0.17763.2565
    • 10.0.17763.2565
    MicrosoftWindows Server 2022
    • 10.0.20348.0 – < 10.0.20348.524
    • 10.0.20348.524
    MicrosoftWindows Server version 20H2
    • 10.0.0 – < 10.0.19042.1526
    • 10.0.19042.1526

    Vendors and products

    Affected operating systems

    Affected operating systems
    Windowsmicrosoftwindows_10_1507—
    Windowsmicrosoftwindows_10_1607—
    Windowsmicrosoftwindows_10_1809—
    Windowsmicrosoftwindows_10_1909—
    Windowsmicrosoftwindows_10_20h2—
    Windowsmicrosoftwindows_10_21h1—
    Windowsmicrosoftwindows_10_21h2—
    Windowsmicrosoftwindows_11_21h2—
    Windowsmicrosoftwindows_7—
    Windowsmicrosoftwindows_8.1—
    Windowsmicrosoftwindows_rt_8.1—
    Windowsmicrosoftwindows_server_2008r2
    Windowsmicrosoftwindows_server_2008—
    Windowsmicrosoftwindows_server_2012r2
    Windowsmicrosoftwindows_server_2012—
    Windowsmicrosoftwindows_server_2016—
    Windowsmicrosoftwindows_server_2019—
    Windowsmicrosoftwindows_server_2022—
    Windowsmicrosoftwindows_server_20h2—

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • Microsoft Security Update GuideWindows Print Spooler Elevation of Privilege VulnerabilityVendor advisory, Patch, Vendor advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2022-22718government-resource, US government resource
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2022-22718
    <a href="https://intel.neosec.eu/en/cve/CVE-2022-22718"><img src="https://intel.neosec.eu/badge/cve/CVE-2022-22718.svg?lang=en" alt="CVE-2022-22718 – NEOSEC Intel" height="20"></a>