# CVE-2021-1675: Microsoft Windows Print Spooler Remote Code Execution

> Attackers can execute arbitrary code with elevated privileges via the Windows Print Spooler service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jun 2021
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-vwmm-qq95-vqhf

## What is CVE-2021-1675?

CVE-2021-1675 is a high-severity code injection vulnerability in Microsoft Windows 10 1507, published on 8 Jun 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Windows Print Spooler Remote Code Execution Vulnerability

## Which versions are affected by CVE-2021-1675?

It affects 15 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 1909, Microsoft Windows 10 2004, Microsoft Windows 10 20h2, Microsoft Windows 10 21h1, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2004, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019.

## How do I fix CVE-2021-1675?

No fix has been published for CVE-2021-1675 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 17 Nov 2021.

## Is CVE-2021-1675 being exploited?

Yes. Attackers have exploited CVE-2021-1675 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Public exploit code:

- C# and Impacket implementation of PrintNightmare CVE-2021-1675/CVE-2021-34527 (github_poc): https://github.com/cube0x0/CVE-2021-1675
- Pure PowerShell implementation of CVE-2021-1675 Print Spooler Local Privilege Escalation (PrintNightmare) (github_poc): https://github.com/calebstewart/CVE-2021-1675
- Local Privilege Escalation Edition for CVE-2021-1675/CVE-2021-34527 (github_poc): https://github.com/hlldz/CVE-2021-1675-LPE
- CVE-2021-1675 Detection Info (github_poc): https://github.com/LaresLLC/CVE-2021-1675
- Python implementation for PrintNightmare (CVE-2021-1675 / CVE-2021-34527) (github_poc): https://github.com/ly4k/PrintNightmare
- PrintNightMare LPE提权漏洞的CS 反射加载插件。开箱即用、通过内存加载、混淆加载的驱动名称来ByPass Defender/EDR。 (github_poc): https://github.com/mstxq17/CVE-2021-1675_RDL_LPE

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-1675 and fix it if it is affected.

What it is: CVE-2021-1675 is a high-severity code injection vulnerability in Microsoft Windows 10 1507, published on 8 Jun 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2021-1675 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-1675/ (Markdown: https://insights.sbomify.com/CVE-2021-1675/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-1675
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-1675
- OSV: https://osv.dev/vulnerability/CVE-2021-1675

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-1675/
Summaries are generated and may contain mistakes; the official description above is the record.