CVE-2022-38028: Microsoft Windows Print Spooler Privilege Escalation
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2024-04-23.
- CVSS v3.1 (CVE record)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 15%
- higher than 96.7% of all CVEs
- Added to CISA KEV
- 2024-04-23
- US federal due date 2024-05-14
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2022-38028 explained
CVE-2022-38028 is a privilege escalation vulnerability in the Microsoft Windows Print Spooler service. An attacker may modify a JavaScript constraints file and have it executed with SYSTEM-level permissions. CISA lists it as known to be exploited, so unpatched Windows clients and servers face a real risk of full system takeover by local attackers.
Impact
An attacker who already has low-privileged local access can gain SYSTEM-level permissions without any user interaction. This means full compromise of confidentiality, integrity and availability on the affected host. CISA rates the technical impact as total but not automatable, so each attack needs manual steps on a target system. Attackers are known to exploit it; whether it is used in ransomware campaigns is unknown.
Who is affected
The CVE record lists Windows 10 versions 1507, 1607, 1809, 20H2, 21H1 and 21H2, Windows 11 versions 21H2 and 22H2, and Windows Server 2016, 2019 (including Server Core) and 2022. Fixed builds include 10.0.17763.3532 (1809, Server 2019), 10.0.19043.2130 (21H1), 10.0.19042.2130 (20H2), 10.0.19044.2130 (10 21H2), 10.0.20348.1129 (Server 2022), 10.0.22000.1098 (11 21H2), 10.0.22621.674 (11 22H2), 10.0.10240.19507 (1507) and 10.0.14393.5427 (1607, Server 2016). The page lists further products.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft Windows Print Spooler service contains a privilege escalation vulnerability. An attacker may modify a JavaScript constraints file and execute it with SYSTEM-level permissions.
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 10 Version 180932-bit, x64, ARM64AffectedFixed in
- < 10.0.17763.3532
- 10.0.17763.3532
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.3532
- 10.0.17763.3532
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.3532
- 10.0.17763.3532
- Microsoft Windows 10 Version 21H1x64, ARM64, 32-bitAffectedFixed in
- < 10.0.19043.2130
- 10.0.19043.2130
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.1129
- 10.0.20348.1129
- Microsoft Windows 10 Version 20H232-bit, ARM64AffectedFixed in
- < 10.0.19042.2130
- 10.0.19042.2130
- Microsoft Windows 11 version 21H2x64, ARM64AffectedFixed in
- < 10.0.22000.1098
- 10.0.22000.1098
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.2130
- 10.0.19044.2130
- Microsoft Windows 11 version 22H2ARM64, x64AffectedFixed in
- < 10.0.22621.674
- 10.0.22621.674
- Microsoft Windows 10 Version 150732-bit, x64AffectedFixed in
- < 10.0.10240.19507
- 10.0.10240.19507
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 180932-bit, x64, ARM64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows 10 Version 20H232-bit, ARM64 |
|
|
| Microsoft Windows 11 version 21H2x64, ARM64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H2ARM64, x64 |
|
|
| Microsoft Windows 10 Version 150732-bit, x64 |
|
|
Show 8 more products
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.5427
- 10.0.14393.5427
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.5427
- 10.0.14393.5427
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.5427
- 10.0.14393.5427
- Microsoft Windows 8.132-bit, x64, ARM64AffectedFixed in
- < 6.3.9600.20625
- 6.3.9600.20625
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.23920
- 6.2.9200.23920
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- < 6.2.9200.23920
- 6.2.9200.23920
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.20625
- 6.3.9600.20625
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- < 6.3.9600.20625
- 6.3.9600.20625
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows 8.132-bit, x64, ARM64 |
|
|
| Microsoft Windows Server 2012x64 |
|
|
| Microsoft Windows Server 2012 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012 R2x64 |
|
|
| Microsoft Windows Server 2012 R2 (Server Core installation)x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1809: 10.0.17763.3532
- Microsoft Windows Server 2019: 10.0.17763.3532
- Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.3532
- Microsoft Windows 10 Version 21H1: 10.0.19043.2130
- Microsoft Windows Server 2022: 10.0.20348.1129
- Microsoft Windows 10 Version 20H2: 10.0.19042.2130
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-38028
- CISA's deadline for US federal agencies: 2024-05-14 (passed) – a useful benchmark for everyone else, too.
What to do
- Install Microsoft's security update so each system reaches the fixed build listed for its Windows version, for example
10.0.20348.1129for Windows Server 2022. - Prioritize servers and shared systems where many users have local accounts, since the flaw needs only low-privileged local access.
- Follow the vendor advisory and apply any mitigations Microsoft describes; CISA requires discontinuing use if mitigations are unavailable.
- Where printing is not needed, consider disabling the Print Spooler service to reduce exposure.
- Check systems for signs of compromise, such as unexpected SYSTEM-level activity linked to the Print Spooler, because the vulnerability is known to be exploited.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Questions about CVE-2022-38028
- Can this be exploited remotely?
- The CVSS vector rates the attack as local. An attacker needs low-privileged access to the system first, but no user interaction. Once in, they can gain SYSTEM-level permissions.
- Is CVE-2022-38028 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-04-23, with a US federal due date of 2024-05-14. Known ransomware use is listed as unknown.
- How do I know if a system is fixed?
- Compare the Windows build number with the fixed build for that version, such as
10.0.17763.3532for Windows 10 Version 1809 and Windows Server 2019. Builds below that number are affected.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.