CVE-2021-1675

HIGHNVD 7.89.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
7.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 85%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Windows Print Spooler Remote Code Execution Vulnerability

CVSS v3
7.8
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
99.7%
KEV
⚠ Exploited

Published

June 8, 2021

Last Modified

October 30, 2025

Advisory Details (5)

Auto-updated Jun 3, 2026
Patch available. Sources: microsoft, cert.
cert

VU#383432 - Microsoft Windows Print Spooler allows for RCE via AddPrinterDriverEx()

https://www.kb.cert.org/vuls/id/383432
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-1675

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 73× in last 7d / 392× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 717 total refreshes for this CVE.

  1. 2026-07-24 14:15 UTCEPSS rescore
  2. 2026-07-23 01:56 UTCEG score recompute
  3. 2026-07-22 22:54 UTCVendor advisory
  4. 2026-07-22 22:54 UTCGHSA enrichment
  5. 2026-07-22 22:42 UTCEG score recompute
  6. 2026-07-22 19:40 UTCCISA KEV update
  7. 2026-07-22 19:13 UTCGHSA enrichment
  8. 2026-07-22 15:31 UTCEG score recompute
  9. 2026-07-22 15:31 UTCVendor advisory
  10. 2026-07-22 15:31 UTCGHSA enrichment
  11. 2026-07-22 14:05 UTCEPSS rescore
  12. 2026-07-22 11:50 UTCVendor advisory
  13. 2026-07-22 11:50 UTCGHSA enrichment
  14. 2026-07-22 08:10 UTCVendor advisory
  15. 2026-07-22 08:10 UTCGHSA enrichment
  16. 2026-07-22 04:29 UTCVendor advisory
  17. 2026-07-22 04:29 UTCGHSA enrichment
  18. 2026-07-22 00:49 UTCVendor advisory
  19. 2026-07-22 00:48 UTCGHSA enrichment
  20. 2026-07-21 21:07 UTCVendor advisory
  21. 2026-07-21 21:07 UTCGHSA enrichment
  22. 2026-07-21 17:25 UTCEG score recompute
  23. 2026-07-21 17:25 UTCVendor advisory
  24. 2026-07-21 17:25 UTCGHSA enrichment
  25. 2026-07-21 15:22 UTCEPSS rescore
Show 75 more
  1. 2026-07-21 15:22 UTCEPSS rescore
  2. 2026-07-21 14:37 UTCCISA KEV update
  3. 2026-07-21 13:44 UTCVendor advisory
  4. 2026-07-21 13:44 UTCGHSA enrichment
  5. 2026-07-21 10:03 UTCVendor advisory
  6. 2026-07-21 10:03 UTCGHSA enrichment
  7. 2026-07-21 06:21 UTCVendor advisory
  8. 2026-07-21 06:21 UTCGHSA enrichment
  9. 2026-07-21 02:40 UTCVendor advisory
  10. 2026-07-21 02:40 UTCGHSA enrichment
  11. 2026-07-20 22:58 UTCVendor advisory
  12. 2026-07-20 22:58 UTCGHSA enrichment
  13. 2026-07-20 19:18 UTCEG score recompute
  14. 2026-07-20 19:18 UTCVendor advisory
  15. 2026-07-20 19:18 UTCGHSA enrichment
  16. 2026-07-20 17:04 UTCEPSS rescore
  17. 2026-07-20 15:38 UTCGHSA enrichment
  18. 2026-07-20 11:57 UTCGHSA enrichment
  19. 2026-07-20 08:17 UTCVendor advisory
  20. 2026-07-20 08:16 UTCGHSA enrichment
  21. 2026-07-20 04:36 UTCVendor advisory
  22. 2026-07-20 04:36 UTCGHSA enrichment
  23. 2026-07-20 00:55 UTCVendor advisory
  24. 2026-07-19 21:15 UTCVendor advisory
  25. 2026-07-19 21:15 UTCGHSA enrichment
  26. 2026-07-19 17:35 UTCVendor advisory
  27. 2026-07-19 17:35 UTCGHSA enrichment
  28. 2026-07-19 13:55 UTCVendor advisory
  29. 2026-07-19 13:55 UTCGHSA enrichment
  30. 2026-07-19 10:15 UTCVendor advisory
  31. 2026-07-19 10:15 UTCGHSA enrichment
  32. 2026-07-19 06:34 UTCVendor advisory
  33. 2026-07-19 06:34 UTCGHSA enrichment
  34. 2026-07-19 02:54 UTCVendor advisory
  35. 2026-07-19 02:54 UTCGHSA enrichment
  36. 2026-07-18 23:13 UTCGHSA enrichment
  37. 2026-07-18 19:32 UTCVendor advisory
  38. 2026-07-18 19:32 UTCGHSA enrichment
  39. 2026-07-18 15:51 UTCVendor advisory
  40. 2026-07-18 15:51 UTCGHSA enrichment
  41. 2026-07-18 12:10 UTCEG score recompute
  42. 2026-07-18 12:10 UTCVendor advisory
  43. 2026-07-18 12:10 UTCGHSA enrichment
  44. 2026-07-18 10:02 UTCEPSS rescore
  45. 2026-07-18 08:29 UTCVendor advisory
  46. 2026-07-18 08:29 UTCGHSA enrichment
  47. 2026-07-18 04:48 UTCVendor advisory
  48. 2026-07-18 04:48 UTCGHSA enrichment
  49. 2026-07-18 01:06 UTCVendor advisory
  50. 2026-07-18 01:06 UTCGHSA enrichment
  51. 2026-07-17 21:26 UTCVendor advisory
  52. 2026-07-17 21:26 UTCGHSA enrichment
  53. 2026-07-17 17:45 UTCVendor advisory
  54. 2026-07-17 17:45 UTCGHSA enrichment
  55. 2026-07-17 14:04 UTCVendor advisory
  56. 2026-07-17 14:04 UTCGHSA enrichment
  57. 2026-07-17 10:23 UTCEG score recompute
  58. 2026-07-17 10:23 UTCVendor advisory
  59. 2026-07-17 10:23 UTCGHSA enrichment
  60. 2026-07-17 06:43 UTCVendor advisory
  61. 2026-07-17 06:43 UTCGHSA enrichment
  62. 2026-07-17 03:03 UTCVendor advisory
  63. 2026-07-17 03:03 UTCGHSA enrichment
  64. 2026-07-16 23:23 UTCVendor advisory
  65. 2026-07-16 23:22 UTCGHSA enrichment
  66. 2026-07-16 19:42 UTCVendor advisory
  67. 2026-07-16 19:42 UTCGHSA enrichment
  68. 2026-07-16 17:04 UTCCISA KEV update
  69. 2026-07-16 16:02 UTCVendor advisory
  70. 2026-07-16 16:02 UTCGHSA enrichment
  71. 2026-07-16 12:22 UTCVendor advisory
  72. 2026-07-16 12:22 UTCGHSA enrichment
  73. 2026-07-16 08:40 UTCGHSA enrichment
  74. 2026-07-16 04:59 UTCVendor advisory
  75. 2026-07-16 04:59 UTCGHSA enrichment

Publicly available exploits

(10 references)

Working exploit code is in the public domain (10 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCly4k/PrintNightmare
    First seen Sep 26, 2021

    Python implementation for PrintNightmare (CVE-2021-1675 / CVE-2021-34527)

    Open source ↗
  • GitHub PoCmstxq17/CVE-2021-1675_RDL_LPE
    First seen Sep 1, 2021

    PrintNightMare LPE提权漏洞的CS 反射加载插件。开箱即用、通过内存加载、混淆加载的驱动名称来ByPass Defender/EDR。

    Open source ↗
  • GitHub PoCJumpsecLabs/PrintNightmare
    First seen Jul 7, 2021

    Information on the Windows Spooler vulnerability - CVE-2021-1675; CVE 2021 34527

    Open source ↗
  • GitHub PoCsailay1996/PrintNightmare-LPE
    First seen Jul 5, 2021

    CVE-2021-1675 (PrintNightmare)

    Open source ↗
  • GitHub PoCcalebstewart/CVE-2021-1675
    First seen Jul 1, 2021

    Pure PowerShell implementation of CVE-2021-1675 Print Spooler Local Privilege Escalation (PrintNightmare)

    Open source ↗
  • GitHub PoChlldz/CVE-2021-1675-LPE
    First seen Jul 1, 2021

    Local Privilege Escalation Edition for CVE-2021-1675/CVE-2021-34527

    Open source ↗
  • GitHub PoCevilashz/CVE-2021-1675-LPE-EXP
    First seen Jul 1, 2021

    PrintNightmare , Local Privilege Escalation of CVE-2021-1675 or CVE-2021-34527

    Open source ↗
  • GitHub PoCcybersecurityworks553/CVE-2021-1675_PrintNightMare
    First seen Jul 1, 2021
    Open source ↗
  • GitHub PoCLaresLLC/CVE-2021-1675
    First seen Jun 30, 2021

    CVE-2021-1675 Detection Info

    Open source ↗
  • GitHub PoCcube0x0/CVE-2021-1675
    First seen Jun 29, 2021

    C# and Impacket implementation of PrintNightmare CVE-2021-1675/CVE-2021-34527

    Open source ↗

Frequently asked(6)

What is CVE-2021-1675?
CVE-2021-1675 is a high vulnerability published on June 8, 2021. Windows Print Spooler Remote Code Execution Vulnerability
When was CVE-2021-1675 disclosed?
CVE-2021-1675 was first published in the National Vulnerability Database on June 8, 2021, with the most recent update on October 30, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-1675 actively exploited?
Yes. CISA added CVE-2021-1675 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft Windows. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2021-1675?
CVE-2021-1675 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2021-1675?
CVE-2021-1675 affects Microsoft Windows. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2021-1675?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-1675, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2021-1675

Explore →

Is Your Infrastructure Affected by CVE-2021-1675?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.