CVE-2021-1675 | Windows Print Spooler Remote Code Execution Vulnerability

Exp

Windows Print Spooler Remote Code Execution Vulnerability

Published: 2021-06-08 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-1675 is rated Critical Active Threat (86.1/100): CVSS High severity, with high exploitation likelihood (EPSS 86.13%, 100th percentile). CISA KEV confirms active exploitation (added 2021-11-03) affecting Microsoft / Windows. Unauthenticated remote administrative access may be possible. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2021-1675

Name: Microsoft Windows Print Spooler Remote Code Execution Vulnerability · CISA KEV detail

Exploit added: 2021-11-03

Action due: 2021-11-17

Required action: Apply updates per vendor instructions.

Public exploit references (Exploit-DB) for CVE-2021-1675

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2021-1675

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 94.31% 86.13% -8.18%
2 2025-11-21 93.62% 94.31% +0.69%
3 2025-11-20 — 93.62% —

Full EPSS history (48 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-1675

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
9.3 2.0 HIGH
AV:N/AC:M/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 8.6 10.0 [email protected]

Weakness enumeration for CVE-2021-1675

Affected software / configurations for CVE-2021-1675

Vendor Product Version Raw CPE
microsoft windows_10_1507 < 10.0.10240.18967 cpe:2.3:o:microsoft:windows_10_1507:*:*:*:*:*:*:*:*
microsoft windows_10_1607 < 10.0.14393.4467 cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:*:*
microsoft windows_10_1809 < 10.0.17763.1999 cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:*:*
microsoft windows_10_1909 < 10.0.18363.1621 cpe:2.3:o:microsoft:windows_10_1909:*:*:*:*:*:*:*:*
microsoft windows_10_2004 < 10.0.19041.1052 cpe:2.3:o:microsoft:windows_10_2004:*:*:*:*:*:*:*:*
microsoft windows_10_20h2 < 10.0.19042.1052 cpe:2.3:o:microsoft:windows_10_20h2:*:*:*:*:*:*:*:*
microsoft windows_10_21h1 < 10.0.19043.1052 cpe:2.3:o:microsoft:windows_10_21h1:*:*:*:*:*:*:*:*
microsoft windows_7 — cpe:2.3:o:microsoft:windows_7:-:sp1:*:*:*:*:*:*
microsoft windows_8.1 — cpe:2.3:o:microsoft:windows_8.1:-:*:*:*:*:*:*:*
microsoft windows_rt_8.1 — cpe:2.3:o:microsoft:windows_rt_8.1:-:*:*:*:*:*:*:*
microsoft windows_server_2004 < 10.0.19041.1052 cpe:2.3:o:microsoft:windows_server_2004:*:*:*:*:*:*:*:*
microsoft windows_server_2008 — cpe:2.3:o:microsoft:windows_server_2008:-:sp2:*:*:*:*:*:*
microsoft windows_server_2008 r2 cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:*:*:*:*:x64:*
microsoft windows_server_2012 — cpe:2.3:o:microsoft:windows_server_2012:-:*:*:*:*:*:*:*
microsoft windows_server_2012 r2 cpe:2.3:o:microsoft:windows_server_2012:r2:*:*:*:*:*:*:*
microsoft windows_server_2016 < 10.0.14393.4467 cpe:2.3:o:microsoft:windows_server_2016:*:*:*:*:*:*:*:*
microsoft windows_server_2019 < 10.0.17763.1999 cpe:2.3:o:microsoft:windows_server_2019:*:*:*:*:*:*:*:*

References for CVE-2021-1675

cvelogic Threat Intelligence