Skip to content
Server Security Center
KEVhigh7.8

CVE-2022-22047: Microsoft Windows Client Server Runtime Subsystem (CSRSS) Privilege Escalation

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-07-12.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
18%
higher than 97.2% of all CVEs
Added to CISA KEV
2022-07-12
US federal due date 2022-08-02
Automatable (CISA SSVC)
no
technical impact: total

CVE-2022-22047 explained

CVE-2022-22047 is a privilege escalation vulnerability in the Client Server Runtime Subsystem (CSRSS) of Microsoft Windows. It lets a user who can already run code on a system gain SYSTEM privileges. CISA lists it as known to be exploited, so unpatched Windows clients and servers should be treated as a priority.

Impact

An attacker with local access and low privileges can raise their rights to SYSTEM without any user interaction. This gives high impact on confidentiality, integrity and availability, and CISA rates the technical impact as total. CISA does not consider it automatable, so each attack needs a foothold on the target first. Attackers are known to exploit it. Whether ransomware groups use it is unknown.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 20H2, 21H1 and 21H2, Windows 11 version 21H2, Windows Server 2016, 2019 (including Server Core), Server 2022 and Server version 20H2. Fixed builds include 10.0.17763.3165 (1809/Server 2019), 10.0.19042.1826, 10.0.19043.1826, 10.0.19044.1826, 10.0.20348.825 (Server 2022), 10.0.22000.795 (Windows 11), 10.0.10240.19360 (1507) and 10.0.14393.5246 (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 CSRSS contains an unspecified vulnerability that allows for privilege escalation to SYSTEM privileges.

CISA required action: Apply updates per vendor instructions.

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, ARM64
    Affected
    • < 10.0.17763.3165
    Fixed in
    • 10.0.17763.3165
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.3165
    Fixed in
    • 10.0.17763.3165
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.3165
    Fixed in
    • 10.0.17763.3165
  • Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit
    Affected
    • < 10.0.19043.1826
    Fixed in
    • 10.0.19043.1826
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.825
    Fixed in
    • 10.0.20348.825
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1826
    Fixed in
    • 10.0.19042.1826
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1826
    Fixed in
    • 10.0.19042.1826
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.795
    Fixed in
    • 10.0.22000.795
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.1826
    Fixed in
    • 10.0.19044.1826
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.19360
    Fixed in
    • 10.0.10240.19360
Show 14 more products
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.5246
    Fixed in
    • 10.0.14393.5246
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.5246
    Fixed in
    • 10.0.14393.5246
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.5246
    Fixed in
    • 10.0.14393.5246
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.26022
    Fixed in
    • 6.1.7601.26022
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.26022
    Fixed in
    • 6.1.7601.26022
  • Microsoft Windows 8.132-bit, x64, ARM64
    Affected
    • < 6.3.9600.20478
    Fixed in
    • 6.3.9600.20478
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.21569
    Fixed in
    • 6.0.6003.21569
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21569
    Fixed in
    • 6.0.6003.21569
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.26022
    Fixed in
    • 6.1.7601.26022
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.26022
    Fixed in
    • 6.1.7601.26022
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23771
    Fixed in
    • 6.2.9200.23771
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23771
    Fixed in
    • 6.2.9200.23771
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20478
    Fixed in
    • 6.3.9600.20478
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20478
    Fixed in
    • 6.3.9600.20478

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.3165
    • Microsoft Windows Server 2019: 10.0.17763.3165
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.3165
    • Microsoft Windows 10 Version 21H1: 10.0.19043.1826
    • Microsoft Windows Server 2022: 10.0.20348.825
    • Microsoft Windows 10 Version 20H2: 10.0.19042.1826
    Fixed versions for 18 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-22047
  • CISA's deadline for US federal agencies: 2022-08-02 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update for each affected Windows version, following the vendor advisory.
  2. Confirm each system reports at least the fixed build listed for its version, such as 10.0.17763.3165 or 10.0.20348.825.
  3. Prioritize servers and multi-user systems, since any low-privileged local user could gain SYSTEM rights.
  4. Limit who can log on locally or run code on critical systems.
  5. Check systems that were unpatched for signs of compromise, as this 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

Weakness: CWE-426 Untrusted Search Path

Questions about CVE-2022-22047

Can this be exploited remotely?
No. The attack vector is local. An attacker needs low-privileged access to the system first, then can escalate to SYSTEM privileges.
Is CVE-2022-22047 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-07-12, with a US federal due date of 2022-08-02. Its required action is to apply updates per vendor instructions.
Which build fixes Windows Server 2022 and Windows 11 21H2?
Windows Server 2022 is fixed in 10.0.20348.825. Windows 11 version 21H2 is fixed in 10.0.22000.795.

Written with AI from the data on this page and checked against it automatically.

References

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.