Skip to content
Server Security Center
KEVhigh7.0

CVE-2022-26904: Microsoft Windows User Profile Service Privilege Escalation

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

CVSS v3.1 (CVE record)
7.0
high
EPSS (exploit probability, 30 days)
17%
higher than 97.1% of all CVEs
Added to CISA KEV
2022-04-25
US federal due date 2022-05-16
Automatable (CISA SSVC)
no
technical impact: total

CVE-2022-26904 explained

CVE-2022-26904 is a privilege escalation vulnerability in the Microsoft Windows User Profile Service, classified as a race condition. CISA lists it as known to be exploited by attackers, so affected Windows desktops and servers should be patched promptly.

Impact

A local attacker who already has low-privileged access can escalate privileges without user interaction. Exploitation requires winning a race condition, so attack complexity is high. Success means high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected system component. CISA rates it as not automatable, so each attack needs manual steps. It is known to be exploited; ransomware use is unknown.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 1909, 20H2, 21H1 and 21H2, Windows 11 version 21H2, and Windows Server 2019 (including Server Core), Server 2022 and Server version 20H2. Fixed builds include 10.0.17763.2803 (1809/Server 2019), 10.0.18363.2212 (1909), 10.0.19042.1645, 10.0.19043.1645, 10.0.19044.1645, 10.0.20348.643 (Server 2022), 10.0.22000.613 (Windows 11), 10.0.10240.19265 (1507) and 10.0.14393.5066 (1607). Further products are listed on this page.

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

Official description

Microsoft Windows User Profile Service contains an unspecified vulnerability that allows for privilege escalation.

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.2803
    Fixed in
    • 10.0.17763.2803
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.2803
    Fixed in
    • 10.0.17763.2803
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.2803
    Fixed in
    • 10.0.17763.2803
  • Microsoft Windows 10 Version 190932-bit, x64, ARM64
    Affected
    • < 10.0.18363.2212
    Fixed in
    • 10.0.18363.2212
  • Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit
    Affected
    • < 10.0.19043.1645
    Fixed in
    • 10.0.19043.1645
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.643
    Fixed in
    • 10.0.20348.643
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1645
    Fixed in
    • 10.0.19042.1645
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1645
    Fixed in
    • 10.0.19042.1645
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.613
    Fixed in
    • 10.0.22000.613
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.1645
    Fixed in
    • 10.0.19044.1645
Show 15 more products
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.19265
    Fixed in
    • 10.0.10240.19265
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.5066
    Fixed in
    • 10.0.14393.5066
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.5066
    Fixed in
    • 10.0.14393.5066
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.5066
    Fixed in
    • 10.0.14393.5066
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.25924
    Fixed in
    • 6.1.7601.25924
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.25924
    Fixed in
    • 6.1.7601.25924
  • Microsoft Windows 8.132-bit, x64, ARM64
    Affected
    • < 6.3.9600.20337
    Fixed in
    • 6.3.9600.20337
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.21446
    Fixed in
    • 6.0.6003.21446
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21446
    Fixed in
    • 6.0.6003.21446
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.25924
    Fixed in
    • 6.1.7601.25924
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.25924
    Fixed in
    • 6.1.7601.25924
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23679
    Fixed in
    • 6.2.9200.23679
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23679
    Fixed in
    • 6.2.9200.23679
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20337
    Fixed in
    • 6.3.9600.20337
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20337
    Fixed in
    • 6.3.9600.20337

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.2803
    • Microsoft Windows Server 2019: 10.0.17763.2803
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.2803
    • Microsoft Windows 10 Version 1909: 10.0.18363.2212
    • Microsoft Windows 10 Version 21H1: 10.0.19043.1645
    • Microsoft Windows Server 2022: 10.0.20348.643
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-26904
  • CISA's deadline for US federal agencies: 2022-05-16 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to the fixed build listed for its Windows version.
  2. Prioritize multi-user systems such as servers and shared workstations, since attackers need local low-privileged access.
  3. Limit local and interactive logon rights to users who need them.
  4. Check systems for signs of unexpected privilege escalation or compromise, given known exploitation.
  5. Follow the Microsoft advisory for full product coverage and update details.

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-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Questions about CVE-2022-26904

Is CVE-2022-26904 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-04-25, with a US federal due date of 2022-05-16. Whether it has been used in ransomware campaigns is unknown.
Can it be exploited remotely?
No. The attack vector is local and requires an attacker who already has low-privileged access to the system. No user interaction is needed, but attack complexity is high.
What does CISA require?
CISA's required action is to apply updates per vendor instructions, meaning installing Microsoft's security update for each affected Windows version.

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.