CVE-2026-21519: Microsoft Windows Type Confusion
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)
- 2.6%
- higher than 85.5% 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-21519 explained
CVE-2026-21519 is a type confusion vulnerability in the Desktop Window Manager of Microsoft Windows. An authorized local attacker can use it to elevate privileges. CISA lists it as known to be exploited, and it affects multiple Windows 10, Windows 11 and Windows Server releases, so prompt patching matters.
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 rates it as not automatable, so each attack needs manual steps. Attackers are known to exploit this vulnerability. Whether it has been used in ransomware campaigns is unknown.
Who is affected
The CVE 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. It lists Windows 11 version 22H3 and Version 23H2 before 10.0.22631.6649, 24H2 before 10.0.26100.7840, 25H2 before 10.0.26200.7840 and 26H1 before 10.0.28000.1575. It also lists Windows Server 2016, including Server Core, before 10.0.14393.8868 and Windows Server 2019 before 10.0.17763.8389. Each listed version is the fix. The page lists further products.
Written with AI from the data on this page and checked against it automatically.
Official description
Access of resource using incompatible type ('type confusion') in Desktop Window Manager 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, x64AffectedFixed in
- < 10.0.14393.8868
- 10.0.14393.8868
- Microsoft Windows 10 Version 180932-bit, x64AffectedFixed in
- < 10.0.17763.8389
- 10.0.17763.8389
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.6937
- 10.0.19044.6937
- Microsoft Windows 10 Version 22H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19045.6937
- 10.0.19045.6937
- Microsoft Windows 11 version 22H3ARM64AffectedFixed in
- < 10.0.22631.6649
- 10.0.22631.6649
- Microsoft Windows 11 Version 23H2x64AffectedFixed in
- < 10.0.22631.6649
- 10.0.22631.6649
- Microsoft Windows 11 Version 24H2ARM64, x64AffectedFixed in
- < 10.0.26100.7840
- 10.0.26100.7840
- Microsoft Windows 11 Version 25H2AffectedFixed in
- < 10.0.26200.7840
- 10.0.26200.7840
- Microsoft Windows 11 version 26H1ARM64AffectedFixed in
- < 10.0.28000.1575
- 10.0.28000.1575
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.8868
- 10.0.14393.8868
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows 10 Version 180932-bit, x64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H3ARM64 |
|
|
| Microsoft Windows 11 Version 23H2x64 |
|
|
| Microsoft Windows 11 Version 24H2ARM64, x64 |
|
|
| Microsoft Windows 11 Version 25H2 |
|
|
| Microsoft Windows 11 version 26H1ARM64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
Show 7 more products
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.8868
- 10.0.14393.8868
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.8389
- 10.0.17763.8389
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.8389
- 10.0.17763.8389
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.4773
- 10.0.20348.4773
- Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64AffectedFixed in
- < 10.0.25398.2149
- 10.0.25398.2149
- Microsoft Windows Server 2025x64AffectedFixed in
- < 10.0.26100.32370
- 10.0.26100.32370
- Microsoft Windows Server 2025 (Server Core installation)x64AffectedFixed in
- < 10.0.26100.32370
- 10.0.26100.32370
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2025x64 |
|
|
| Microsoft Windows Server 2025 (Server Core installation)x64 |
|
|
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
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21519
- CISA's deadline for US federal agencies: 2026-03-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the Microsoft security update that brings each system to the fixed build listed for its Windows release.
- Prioritize systems where many users log on locally or remotely, such as shared workstations and terminal servers.
- Follow the Microsoft advisory and CISA's required action; U.S. federal agencies must act by 2026-03-03.
- Limit local and interactive logon rights to accounts that need them.
- Check systems for signs of unexpected privilege escalation or compromise, since 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
Weakness: CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')
Questions about CVE-2026-21519
- Can this be exploited remotely?
- No. The attack vector is local. The attacker needs an authorized, low-privileged account on the system. No user interaction is required.
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2026-21519 to its Known Exploited Vulnerabilities catalog on 2026-02-10. Whether it has been used in ransomware campaigns is unknown.
- Which build fixes the issue on Windows 11 Version 24H2?
- The CVE record names
10.0.26100.7840as the fixed version for Windows 11 Version 24H2. Earlier builds 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-21. Always confirm with the vendor's or distribution's advisory before patching.