Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 17 Nov 2021. Known ransomware use
Windows 10 1507Operating system · Microsoft

CVE-2021-1675

HIGH · 7.8 CVSS v3.1 Published 2021-06-08
Fix available
A fix is available. Upgrade to 10.0.10240.18967 / 10.0.14393.4467 or later.
See remediation →
97/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windows Print Spooler Remote Code Execution Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Remote Code Execution vulnerability in the Windows Print Spooler service. The vulnerability allows an attacker to execute arbitrary code on affected Windows systems through the Print Spooler component.

MitigationApply the Microsoft security update for CVE-2021-1675. As a temporary measure, consider disabling the Print Spooler service if not required, or restricting Point and Print connections via Group Policy.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.18967
Windows 10 1607Operating system
Affected:< 10.0.14393.4467
Windows 10 1809Operating system
Affected:< 10.0.17763.1999
Windows 10 1909Operating system
Affected:< 10.0.18363.1621
Windows 10 2004Operating system
Affected:< 10.0.19041.1052
Windows 10 20h2Operating system
Affected:< 10.0.19042.1052
Windows 10 21h1Operating system
Affected:< 10.0.19043.1052
Windows 7Operating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build number
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to see the full build number
    Affected if The build number is lower than the patched version for your Windows 10 release (10240.18967 for 1507, 14393.4467 for 1607, 17763.1999 for 1809, 18363.1621 for 1909, 19041.1052 for 2004/20h2, 19043.1052 for 21h1) or you are on Windows 7 (all versions affected)
  2. Verify Print Spooler service status
    Open PowerShell and run 'Get-Service -Name Spooler' or run 'sc query Spooler' in Command Prompt
    Affected if The service shows as Running (State: Running) - only running services are exploitable
  3. Confirm Print Spooler is enabled for remote connections
    Check registry key 'HKLM\SYSTEM\CurrentControlSet\Services\Spooler' for value 'Start' (4 = disabled, 3 = manual, 2 = automatic). Also verify printer ports are listening with 'netstat -an | findstr :515' or check if any printers are installed via 'Get-Printer' in PowerShell
    Affected if The service is set to start automatically (Start value = 2 or 3) and is running, or the system has printers configured or printing is actively used

Your system is affected if it runs a vulnerable Windows version with the Print Spooler service enabled and running.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.18967 / 10.0.14393.4467 / 10.0.17763.1999 or later
Fixed in 10.0.10240.1896710.0.14393.446710.0.17763.1999
Interim mitigation

Apply the Microsoft security update for CVE-2021-1675. As a temporary measure, consider disabling the Print Spooler service if not required, or restricting Point and Print connections via Group Policy.

Recommended fix High confidence

Windows 10 21h1 (build 10.0.19043.1052+) or Windows 11 recommended; for older versions, upgrade to the specific patched build for your release channel

  1. Identify the current Windows version and build by running 'winver' or 'systeminfo'
  2. For Windows 10 versions 1507 through 21h1: Navigate to Settings > Update & Security > Windows Update and check for updates
  3. Install the cumulative security update that includes the fix for CVE-2021-1675 (KB5001402 or later cumulative updates)
  4. Verify the installed build matches or exceeds the fixed version: 10.0.10240.18967 (1507), 10.0.14393.4467 (1607), 10.0.17763.1999 (1809), 10.0.18363.1621 (1909), 10.0.19041.1052 (2004), 10.0.19042.1052 (20h2), or 10.0.19043.1052 (21h1)
  5. For Windows 7: Upgrade to a supported Windows version (Windows 10 or 11) as Windows 7 is end-of-life and receives no security patches
  6. Alternatively, if upgrading is not immediately possible, disable the Print Spooler service: Run 'net stop spooler' and set the service to Disabled via services.msc
Caveat Windows 7 systems cannot receive patches and must be migrated to a supported OS; ensure application compatibility before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1675 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-1675 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data