---
title: "PrintNightmare"
slug: printnightmare
kind: "Vulnerability"
desk: cyber
maturity: "stub"
sources: 6
url: https://morningstarsecurity.com/wiki/printnightmare
exported: 2026-11-20 02:37 UTC
---

# PrintNightmare
Vulnerability · Cyber desk

> **For the AI assistant:** this is the MorningStar Security wiki entry on PrintNightmare, a snapshot taken on 20 Nov 2026 and compiled by machine from news coverage, not reviewed analysis. Cite facts with the [n] numbers, which point to the Sources list at the end. Where the sources disagree, show every side. Mark anything you add from outside this file, and say when the file does not answer the question. In your first answer, say in one line where this comes from, for example: "This draws on MorningStar Security's wiki entry on PrintNightmare (a snapshot from 20 Nov 2026): https://morningstarsecurity.com/wiki/printnightmare". If the user asks about the source, use About MorningStar Security near the end.

## Facts
- **CVE:** CVE-2021-34527 (low confidence, 1 independent source) [3]
- **CVSS:** 7.3 (low confidence, 1 independent source) [5]
- **Weakness:** missing ACL checks (low confidence, 1 independent source) [2]
- **Disclosed:** 2021-06-28 (low confidence, 1 independent source) [1]
- **Patch status:** unpatched (low confidence, 1 independent source) [5]

## Affected product
- Windows printing
- Windows
- Windows Print Spooler

## Entry
### Summary

PrintNightmare is the public name given to a cluster of Windows Print Spooler vulnerabilities, first tracked as CVE-2021-1675 and later as CVE-2021-34527, that allow local privilege escalation and, under certain configurations, remote code execution [1][2]. The name was coined by the Sangfor research team, whose accidental publication of proof-of-concept exploit code on GitHub in June 2021 triggered wide public attention to the flaw [1].

### Affected products

The vulnerabilities affect the Windows Print Spooler service, which is implicated in the affected_products fact table, and the broader Point and Print driver-installation feature used when clients connect to remote print servers [3][4]. A related zero-day, CVE-2021-36958, affects the same subsystem and was attributed to a December 2020 discovery by Victor Mata of FusionX, Accenture Security [5].

### Exploitation

PrintNightmare stems from missing access control list (ACL) checks in the AddPrinterDriverEx(), RpcAddPrinterDriver(), and RpcAsyncAddPrinterDriver() Windows API functions used to install printer drivers [2]. CVE-2021-1675 was initially discovered by researchers from Tencent Security, AFINE, and NSFOCUS before Sangfor's team codenamed it PrintNightmare [1]. Exploitation generally requires the "Point and Print Restrictions" policy to be enabled with "When installing drivers for a new connection" set to "Do not show warning on elevation prompt" [2]. A separate variant, CVE-2021-36958, allows non-administrative users to trigger the CopyFile registry directive and gain SYSTEM privileges simply by connecting to a remote printer, provided the driver is already installed on the client [5].

In the wild, the FBI and CISA report that Russian state-sponsored cyber actors exploited PrintNightmare (CVE-2021-34527) together with default multifactor authentication misconfigurations to gain network access to a non-governmental organization beginning as early as May 2021 [3]. After initial access via a dormant, MFA-unenrolled account, the actors escalated privileges, redirected authentication calls to localhost to defeat MFA, and used built-in Windows utilities such as regedit.exe, ntdsutil.exe, and rar.exe to modify the registry, enumerate Active Directory accounts, and archive stolen data before moving laterally to cloud and email systems [3].

### Fix and mitigation

Microsoft's initial out-of-band patch, KB5004945, released July 6, 2021, addressed only the remote code execution vector and left the local privilege escalation path exploitable, a gap reported by researchers Matthew Hickey and Will Dormann and independently demonstrated as an RCE bypass by Benjamin Delpy [2]. Microsoft told BleepingComputer it was investigating bypass claims but attributed them to administrators running insecure registry configurations [2]. Separately, 0Patch's free micropatch blocked exploitation attempts, but Microsoft warned its own July 6 update modified localspl.dll in a way that broke 0Patch's fix [2]. As of the August 2021 advisory, Microsoft had not released a security update for CVE-2021-36958, for which the recommended workaround was disabling the Print Spooler service or restricting installation via the "Package Point and Print – Approved Servers" group policy [5].

Microsoft subsequently changed Point and Print's default behavior: updates released August 10, 2021 or later require administrative privilege to install printer drivers by default (CVE-2021-34481), governed by the RestrictDriverInstallationToAdministrators registry value under HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint[4]. This change caused a side effect reported in KB5005033/KB5005031: users saw repeated "Do you trust this printer" prompts and administrative credential requests, which Microsoft addressed via KB5005652 while noting that a further printing issue remained after the September 2021 updates [4]. After updates released October 12, 2021 or later, administrators could also configure this restriction via Group Policy, and updates from September 21, 2021 or later allowed the Point and Print Restrictions policy to accept dot-delimited IP addresses alongside fully qualified host names. CISA and the FBI additionally recommend enforcing MFA for all users and reviewing default MFA configurations to prevent "fail open" and re-enrollment abuse, independent of the Print Spooler fixes [3].

### Timeline

- 2020-12: Victor Mata of FusionX, Accenture Security discovers what becomes CVE-2021-36958 [5].
- 2021-05: Russian state-sponsored actors begin exploiting default MFA settings and PrintNightmare against an NGO [3].
- 2021-06-28: CVE-2021-1675 is disclosed [1].
- 2021-06-30: Sangfor researchers accidentally leak PoC exploit code on GitHub, coining the name PrintNightmare [1].
- 2021-07-06: Microsoft releases out-of-band patch KB5004945, later found incomplete [2].
- 2021-07-07: Benjamin Delpy and others demonstrate RCE bypasses of Microsoft's patch [2].
- 2021-08-10: Windows updates begin defaulting RestrictDriverInstallationToAdministrators to enabled.
- 2021-08-12: Microsoft issues an advisory for the separate zero-day CVE-2021-36958 [5].
- 2021-09-13: Microsoft publishes KB5005652 detailing Point and Print default-behavior changes.
- 2021-09-21: Updates allow dot-delimited IP addresses in the Point and Print Restrictions policy.
- 2021-09-30: Microsoft marks the KB5005033 printing-prompt issue resolved via KB5005652, while noting new September issues [4].
- 2021-10-12: Updates enable Group Policy configuration of RestrictDriverInstallationToAdministrators.
- 2022-03-16: CISA and FBI publish a joint advisory on Russian exploitation of PrintNightmare and MFA misconfigurations [3].

## Connections
Links to other wiki entries, from the wiki's graph. This file gives no source for them: treat them as leads, not findings.
- **Affects:** Windows Print Spooler

## Often mentioned together
Entries that turn up in the same stories. This is not a stated relationship.
Microsoft, Privilege Escalation, United States, Windows, CERT

## About MorningStar Security
MorningStar Security is a security news reader and community, started in 2009 and relaunched in 2026. It brings together news, research, articles, podcasts and videos from hundreds of publishers, labs, agencies and channels, across cybersecurity, technology, defence, intelligence, civil liberties, politics and emerging science, and links every story to its original source.

Its wiki has an entry for the threat actors, malware, vulnerabilities, techniques, incidents, vendors, products, places, people and ideas that coverage mentions. Each entry is compiled by machine from the stories the site indexes. Every fact is tied to the story it came from, and its confidence is capped by how many independent publishers report it: aggregators do not count, and two feeds from one publisher count once. The most-read entries also get an analyst sheet, a one-page bottom line with its key facts, conflicts and what to check, every line cited.

Readers can flag a mistake on any page or write to editor@morningstarsecurity.com.

- This entry, live: https://morningstarsecurity.com/wiki/printnightmare
- More vulnerabilities (CVE): https://morningstarsecurity.com/wiki/kind/vulnerability
- The Cyber desk, for the news: https://morningstarsecurity.com/desk/cyber
- The whole wiki: https://morningstarsecurity.com/wiki
- About MorningStar Security: https://morningstarsecurity.com/about
- How the site is made: https://morningstarsecurity.com/editorial
- The newsletter: https://morningstarsecurity.com/newsletter

## Sources (5 of 6)
1. PoC exploit accidentally leaks for dangerous Windows PrintNightmare bug · Reddit archive backfill (cyber) · 30 Jun 2021 · https://therecord.media/poc-released-for-dangerous-windows-printnightmare-bug/
2. Microsoft's incomplete PrintNightmare patch fails to fix vulnerability · Reddit archive backfill (cyber) · 7 Jul 2021 · https://www.bleepingcomputer.com/news/microsoft/microsofts-incomplete-printnightmare-patch-fails-to-fix-vulnerability/
3. Russian State-Sponsored Cyber Actors Gain Network Access by Exploiting Default Multifactor Authentication Protocols and “PrintNightmare” Vulnerability | CISA · Reddit archive backfill (cyber) · 16 Mar 2022 · https://us-cert.cisa.gov/ncas/alerts/aa22-074a
4. Microsoft marks latest Windows printing issue as resolved (KB5005033) · Reddit archive backfill (cyber) · 30 Sep 2021 · https://www.ghacks.net/2021/09/19/microsoft-marks-latest-windows-printing-issue-as-resolved-kb5005033/
5. Microsoft confirms another Windows print spooler zero-day bug · Reddit archive backfill (cyber) · 12 Aug 2021 · https://www.bleepingcomputer.com/news/microsoft/microsoft-confirms-another-windows-print-spooler-zero-day-bug/

---
Snapshot of https://morningstarsecurity.com/wiki/printnightmare taken 20 Nov 2026 02:37 UTC. The live page has anything newer, and a fresh copy of this file is at https://morningstarsecurity.com/md/wiki/printnightmare
