CVE Intelligence
CISA KEV High exploit reference

CVE-2021-34527 — Microsoft Windows Print Spooler Remote Code Execution Vulnerability

A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. UPDATE July 7, 2021: The security update for Windows Server 2012, Windows Server 2016 and Windows 10, Version 1607 have been released. Please see the Security Updates table for the applicable update for your system. We recommend that you install these updates immediately. If you are unable to install these updates, see the FAQ and Workaround sections in this CVE for information on how to help protect your system from this vulnerability. In addition to installing the updates, in order to secure your system, you must confirm that the following registry settings are set to 0 (zero) or are not defined (Note: These registry keys do not exist by default, and therefore are already at the secure setting.), also that your Group Policy setting are correct (see FAQ): HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PointAndPrint NoWarningNoElevationOnInstall = 0 (DWORD) or not defined (default setting) UpdatePromptSettings = 0 (DWORD) or not defined (default setting) Having NoWarningNoElevationOnInstall set to 1 makes your system vulnerable by design. UPDATE July 6, 2021: Microsoft has completed the investigation and has released security updates to address this vulnerability. Please see the Security Updates table for the applicable update for your system. We recommend that you install these updates immediately. If you are unable to install these updates, see the FAQ and Workaround sections in this CVE for information on how to help protect your system from this vulnerability. See also KB5005010: Restricting installation of new printer drivers after applying the July 6, 2021 updates. Note that the security updates released on and after July 6, 2021 contain protections for CVE-2021-1675 and the additional remote code execution exploit in the Windows Print Spooler service known as “PrintNightmare”, documented in CVE-2021-34527.

Published Jul 2, 2021 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: microsoft

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Used in ransomware campaigns (CISA)+10
  • Public exploit/PoC (metasploit, github)+18
  • EPSS 99.8% (30-day exploitation probability)+15
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Nov 3, 2021
EPSS FIRST
99.79%
ahead of 100% of scored CVEs · Oct 14, 2026
Affects
Microsoft
Windows 10 1507 and 33 more
CVSS base
8.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: May 3, 2022 — passed 1626 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Microsoft Windows 10 1507 < 10.0.10240.18969 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 1607 < 10.0.14393.4470 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 1809 < 10.0.17763.2029 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 20h2 < 10.0.19042.1083 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 21h2 < 10.0.19044.1415 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 22h2 < 10.0.19045.2251 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 Version 1507 ≥ 10.0.10240.0 and < 10.0.10240.18969 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 1607 ≥ 10.0.14393.0 and < 10.0.14393.4470 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 1809 ≥ 10.0.0 and < 10.0.17763.2029≥ 10.0.17763.0 and < 10.0.17763.2029 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 20H2 ≥ 10.0.0 and < 10.0.19042.1083 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 21H2 ≥ 10.0.19044.0 and < 10.0.19044.1415 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 22H2 ≥ 10.0.19045.0 and < 10.0.19045.2251 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 21h2 < 10.0.22000.318 Vulnerable NIST National Vulnerability Database
Microsoft Windows 11 22h2 < 10.0.22621.674 Vulnerable NIST National Vulnerability Database
Microsoft Windows 11 version 21H2 ≥ 10.0.22000.0 and < 10.0.22000.318 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 version 22H2 ≥ 10.0.22621.0 and < 10.0.22621.674 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 8.1 ≥ 6.3.0 and < 6.3.9600.20046 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Rt 8.1 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2008 version r2-sp1versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2008 R2 Service Pack 1 ≥ 6.1.7601.0 and < 6.1.7601.25633 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) ≥ 6.1.7601.0 and < 6.1.7601.25633 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2008 Service Pack 2 ≥ 6.0.6003.0 and < 6.0.6003.21138 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) ≥ 6.0.6003.0 and < 6.0.6003.21138 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2012 ≥ 6.2.9200.0 and < 6.2.9200.23383 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2012 version r2versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2012 (Server Core installation) ≥ 6.2.9200.0 and < 6.2.9200.23383 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2012 R2 ≥ 6.3.9600.0 and < 6.3.9600.20046 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2012 R2 (Server Core installation) ≥ 6.3.9600.0 and < 6.3.9600.20046 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2016 < 10.0.14393.4470 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2016 ≥ 10.0.14393.0 and < 10.0.14393.4470 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2016 (Server Core installation) ≥ 10.0.14393.0 and < 10.0.14393.4470 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2019 ≥ 10.0.17763.0 and < 10.0.17763.2029 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2019 < 10.0.17763.2029 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2019 (Server Core installation) ≥ 10.0.17763.0 and < 10.0.17763.2029 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2022 < 10.0.20348.230 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2022 ≥ 10.0.20348.0 and < 10.0.20348.230 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 20h2 < 10.0.19042.1083 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server version 20H2 ≥ 10.0.0 and < 10.0.19042.1083 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.8 CVSS 3.1 High 2.8 5.9 secure@microsoft.com via NIST National Vulnerability Database
8.8 CVSS 3.1 High 2.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
8.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.8 CVSS 3.1 High — — microsoft via CVE Program (cve.org) e CISA ADP
9.0 CVSS 2.0 High 8.0 10.0 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: secure@microsoft.com)

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Nov 3, 2021
Federal deadline
May 3, 2022
passed 1626 day(s) ago
Ransomware use
Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Metasploit modules

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

Associated ransomware groups ransomware.live

contivicesociety

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 99.79%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Hunt retroactively in logs from before Nov 3, 2021 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · microsoft/windows 10 version 1507, microsoft/windows 10 version 1607, microsoft/windows 10 version 1809, microsoft/windo
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · microsoft/windows 10 1507, microsoft/windows 10 1607, microsoft/windows 10 1809, microsoft/windows 10 20h2, microsoft/wi
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2021
  • Added to CISA KEV catalog
    Nov 2, 2021 · CISA
  • CVE published
    Jul 2, 2021 · microsoft

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

9 on the record

Elsewhere on this site

Microsoft
every CVE for this vendor
2021-11
what else CISA listed that month

Related CVEs (same products)

  • Medium CVE-2026-97844 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97839 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97840 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97841 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97842 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97843 Role: DNS Server Information Disclosure Vulnerability 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2021-34527 is "Microsoft Windows Print Spooler Remote Code Execution Vulnerability", rated High. It affects Windows 10 1507 (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.8 describes technical severity. EPSS 99.79% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.