CVE-2021-34527: 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)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 99.7%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2021-34527 explained
CVE-2021-34527, known as "PrintNightmare", is a remote code execution vulnerability in the Windows Print Spooler service, which improperly performs privileged file operations. Successful exploitation lets an attacker run arbitrary code with SYSTEM privileges. CISA lists it as known exploited and notes known ransomware use, making it a priority for Windows clients and servers.
Impact
An attacker with low privileges can exploit this over the network without user interaction. Successful exploitation runs arbitrary code with SYSTEM privileges, allowing the attacker to install programs, view, change or delete data, or create new accounts with full user rights. CISA rates the technical impact as total but not automatable. Attackers are known to exploit it, including in ransomware campaigns.
Who is affected
The CVE record lists many Windows versions, including Windows 10 Versions 1507, 1607, 1809, 20H2, 21H2 and 22H2, Windows 11 versions 21H2 and 22H2, Windows 8.1, and Windows Server 2008 SP2 and 2008 R2 SP1. Example fixed builds: 10.0.14393.4470 (1607), 10.0.17763.2029 (1809), 10.0.22621.674 (Windows 11 22H2), 6.1.7601.25633 (Server 2008 R2 SP1). Further products are listed on the page.
Written with AI from the data on this page and checked against it automatically.
Official description
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.
CISA required action: Apply updates per vendor instructions.
CISA notes
- Reference CISA's ED 21-04 (cisa.gov/news-events/directives/ed-21-04-mitigate-windows…) for further guidance and requirements. Note: The due date for addressing this vulnerability aligns with the requirements outlined in ED 21-04. nvd.nist.gov/vuln/detail/CVE-2021-34527
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 10 Version 150732-bit, x64AffectedFixed in
- < 10.0.10240.18969
- 10.0.10240.18969
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.4470
- 10.0.14393.4470
- Microsoft Windows 10 Version 180932-bit, x64, ARM64AffectedFixed in
- < 10.0.17763.2029
- 10.0.17763.2029
- Microsoft Windows 10 Version 20H232-bit, ARM64AffectedFixed in
- < 10.0.19042.1083
- 10.0.19042.1083
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.1415
- 10.0.19044.1415
- Microsoft Windows 10 Version 22H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19045.2251
- 10.0.19045.2251
- Microsoft Windows 11 version 21H2ARM64, x64AffectedFixed in
- < 10.0.22000.318
- 10.0.22000.318
- Microsoft Windows 11 version 22H2ARM64, x64AffectedFixed in
- < 10.0.22621.674
- 10.0.22621.674
- Microsoft Windows 8.1ARM64AffectedFixed in
- < 6.3.9600.20046
- 6.3.9600.20046
- Microsoft Windows Server 2008 R2 Service Pack 1x64AffectedFixed in
- < 6.1.7601.25633
- 6.1.7601.25633
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 150732-bit, x64 |
|
|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows 10 Version 180932-bit, x64, ARM64 |
|
|
| Microsoft Windows 10 Version 20H232-bit, ARM64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 21H2ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H2ARM64, x64 |
|
|
| Microsoft Windows 8.1ARM64 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1x64 |
|
|
Show 13 more products
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64AffectedFixed in
- < 6.1.7601.25633
- 6.1.7601.25633
- Microsoft Windows Server 2008 Service Pack 232-bit, x64AffectedFixed in
- < 6.0.6003.21138
- 6.0.6003.21138
- Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64AffectedFixed in
- < 6.0.6003.21138
- 6.0.6003.21138
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.23383
- 6.2.9200.23383
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- < 6.2.9200.23383
- 6.2.9200.23383
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.20046
- 6.3.9600.20046
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- < 6.3.9600.20046
- 6.3.9600.20046
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.4470
- 10.0.14393.4470
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.4470
- 10.0.14393.4470
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.2029
- 10.0.17763.2029
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.2029
- 10.0.17763.2029
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.230
- 10.0.20348.230
- Microsoft Windows Server version 20H2x64AffectedFixed in
- < 10.0.19042.1083
- 10.0.19042.1083
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2008 Service Pack 232-bit, x64 |
|
|
| Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64 |
|
|
| Microsoft Windows Server 2012x64 |
|
|
| Microsoft Windows Server 2012 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012 R2x64 |
|
|
| Microsoft Windows Server 2012 R2 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows Server version 20H2x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1507: 10.0.10240.18969
- Microsoft Windows 10 Version 1607: 10.0.14393.4470
- Microsoft Windows 10 Version 1809: 10.0.17763.2029
- Microsoft Windows 10 Version 20H2: 10.0.19042.1083
- Microsoft Windows 10 Version 21H2: 10.0.19044.1415
- Microsoft Windows 10 Version 22H2: 10.0.19045.2251
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2021-34527
- CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the Microsoft security updates released on or after July 6, 2021 that apply to each affected Windows version.
- After updating, confirm NoWarningNoElevationOnInstall and UpdatePromptSettings under the PointAndPrint policy key are set to 0 or not defined.
- Check Group Policy Point and Print settings as described in the vendor advisory FAQ.
- Review KB5005010 on restricting installation of new printer drivers after the July 2021 updates.
- If updates cannot be installed immediately, apply the workarounds in the vendor advisory.
- Check systems for signs of compromise, such as unexpected new accounts or installed programs.
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-269
Questions about CVE-2021-34527
- Is installing the update enough?
- No. Microsoft states you must also confirm that NoWarningNoElevationOnInstall and UpdatePromptSettings are set to 0 or not defined, and that Group Policy settings are correct. Setting NoWarningNoElevationOnInstall to 1 makes a system vulnerable by design.
- Is this vulnerability being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03 and notes known ransomware use. The required action is to apply updates per vendor instructions.
- How does this relate to CVE-2021-1675?
- Microsoft states that the security updates released on and after July 6, 2021 contain protections for both CVE-2021-1675 and the additional Print Spooler exploit known as PrintNightmare, documented in CVE-2021-34527.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
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.