Skip to content
Server Security Center
KEVhigh7.8

CVE-2026-21533: Microsoft Windows Improper Privilege Management

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2026-02-10.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
4.3%
higher than 91.4% of all CVEs
Added to CISA KEV
2026-02-10
US federal due date 2026-03-03
Automatable (CISA SSVC)
no
technical impact: total

CVE-2026-21533 explained

CVE-2026-21533 is an improper privilege management flaw in Windows Remote Desktop. An authorized local attacker can use it to elevate privileges on affected Windows 10, Windows 11 and Windows Server systems. CISA lists it as known to be exploited, so patching should be treated as urgent.

Impact

An attacker who already has low-privileged local access can elevate privileges without user interaction. Successful exploitation has high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA does not rate it as automatable, meaning it is not exploitable at scale without manual steps. Attackers are known to use this vulnerability; ransomware use is listed as unknown.

Who is affected

The record lists Windows 10 Version 1607 before 10.0.14393.8868, 1809 before 10.0.17763.8389, 21H2 before 10.0.19044.6937 and 22H2 before 10.0.19045.6937. Windows 11 22H3 and 23H2 are fixed in 10.0.22631.6649, 24H2 in 10.0.26100.7840, 25H2 in 10.0.26200.7840 and 26H1 in 10.0.28000.1575. Windows Server 2012 (including Server Core) is fixed in 6.2.9200.25923 and Server 2012 R2 in 6.3.9600.23022. Nine further products are listed on this page; check the vendor advisory for their fixed builds.

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

Official description

Improper privilege management in Windows Remote Desktop allows an authorized attacker to elevate privileges locally.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, 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 160732-bit, x64
    Affected
    • < 10.0.14393.8868
    Fixed in
    • 10.0.14393.8868
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.8389
    Fixed in
    • 10.0.17763.8389
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.6937
    Fixed in
    • 10.0.19044.6937
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.6937
    Fixed in
    • 10.0.19045.6937
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.6649
    Fixed in
    • 10.0.22631.6649
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.6649
    Fixed in
    • 10.0.22631.6649
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.7840
    Fixed in
    • 10.0.26100.7840
  • Microsoft Windows 11 Version 25H2
    Affected
    • < 10.0.26200.7840
    Fixed in
    • 10.0.26200.7840
  • Microsoft Windows 11 version 26H1ARM64
    Affected
    • < 10.0.28000.1575
    Fixed in
    • 10.0.28000.1575
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25923
    Fixed in
    • 6.2.9200.25923
Show 11 more products
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25923
    Fixed in
    • 6.2.9200.25923
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.23022
    Fixed in
    • 6.3.9600.23022
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.23022
    Fixed in
    • 6.3.9600.23022
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.8868
    Fixed in
    • 10.0.14393.8868
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.8868
    Fixed in
    • 10.0.14393.8868
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.8389
    Fixed in
    • 10.0.17763.8389
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.8389
    Fixed in
    • 10.0.17763.8389
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.4773
    Fixed in
    • 10.0.20348.4773
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.2149
    Fixed in
    • 10.0.25398.2149
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.32370
    Fixed in
    • 10.0.26100.32370
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.32370
    Fixed in
    • 10.0.26100.32370

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1607: 10.0.14393.8868
    • Microsoft Windows 10 Version 1809: 10.0.17763.8389
    • Microsoft Windows 10 Version 21H2: 10.0.19044.6937
    • Microsoft Windows 10 Version 22H2: 10.0.19045.6937
    • Microsoft Windows 11 version 22H3: 10.0.22631.6649
    • Microsoft Windows 11 Version 23H2: 10.0.22631.6649
    Fixed versions for 15 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21533
  • CISA's deadline for US federal agencies: 2026-03-03 (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. Check the vendor advisory for the further listed products and their fixed builds.
  3. Prioritize systems where many users have local or Remote Desktop access, such as shared servers.
  4. Limit local and Remote Desktop access to users who need it, and keep Remote Desktop off the internet.
  5. Review affected systems for signs of compromise, such as unexpected privileged accounts or activity.

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-269 Improper Privilege Management

Questions about CVE-2026-21533

Can this be exploited remotely without credentials?
No. The attack vector is local and the attacker needs low privileges on the system. The risk is that an attacker or malware with a standard account gains full control of the machine.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-02-10, with a US federal due date of 2026-03-03. Whether it is used in ransomware campaigns is listed as unknown.
Which build fixes Windows 11 Version 24H2?
The CVE record lists 10.0.26100.7840 as the fixed build for Windows 11 Version 24H2. Earlier builds are affected.

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-21. Always confirm with the vendor's or distribution's advisory before patching.