Skip to content
Server Security Center
KEVhigh7.8

CVE-2022-21971: Microsoft Windows Runtime Remote Code Execution

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

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

CVE-2022-21971 explained

CVE-2022-21971 is a remote code execution vulnerability in Microsoft Windows Runtime, tied to access of an uninitialized pointer. It affects specific Windows 10, Windows 11 and Windows Server builds listed in the CVE record. CISA lists it as known to be exploited, so unpatched systems face real risk.

Impact

Successful exploitation allows code execution with high impact on confidentiality, integrity and availability. The CVSS vector shows a local attack vector, low complexity and no privileges required, but user interaction is needed. CISA's SSVC rates technical impact as total, meaning full control of the affected component, and rates automatable as no. CISA's catalog marks the vulnerability as known to be exploited. Known ransomware use is listed as unknown.

Who is affected

The record lists Windows 10 Version 1809, Windows Server 2019 and its Server Core installation before 10.0.17763.2565; Windows 10 Version 1909 before 10.0.18363.2094; Windows 10 Version 21H1 before 10.0.19043.1526; Windows 10 Version 20H2 and Windows Server version 20H2 before 10.0.19042.1526; Windows 10 Version 21H2 before 10.0.19044.1526; Windows Server 2022 before 10.0.20348.524; and Windows 11 version 21H2 before 10.0.22000.493. Each listed fixed build contains the fix.

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

Official description

Microsoft Windows Runtime contains an unspecified vulnerability that allows for remote code execution.

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.2565
    Fixed in
    • 10.0.17763.2565
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.2565
    Fixed in
    • 10.0.17763.2565
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.2565
    Fixed in
    • 10.0.17763.2565
  • Microsoft Windows 10 Version 190932-bit, x64, ARM64
    Affected
    • < 10.0.18363.2094
    Fixed in
    • 10.0.18363.2094
  • Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit
    Affected
    • < 10.0.19043.1526
    Fixed in
    • 10.0.19043.1526
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.524
    Fixed in
    • 10.0.20348.524
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1526
    Fixed in
    • 10.0.19042.1526
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1526
    Fixed in
    • 10.0.19042.1526
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.493
    Fixed in
    • 10.0.22000.493
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.1526
    Fixed in
    • 10.0.19044.1526

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.2565
    • Microsoft Windows Server 2019: 10.0.17763.2565
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.2565
    • Microsoft Windows 10 Version 1909: 10.0.18363.2094
    • Microsoft Windows 10 Version 21H1: 10.0.19043.1526
    • Microsoft Windows Server 2022: 10.0.20348.524
    Fixed versions for 4 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-21971
  • CISA's deadline for US federal agencies: 2022-09-08 (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. Verify build numbers across the fleet, including Server Core installations, to confirm no system remains below the fixed build.
  3. Follow the Microsoft advisory and CISA's required action: apply updates per vendor instructions.
  4. Because user interaction is required, remind users not to open untrusted files or content.
  5. Review systems that were unpatched for signs of compromise, given confirmed exploitation.

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-824 Access of Uninitialized Pointer

Questions about CVE-2022-21971

Is CVE-2022-21971 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-08-18, with a US federal due date of 2022-09-08. Whether it has been used in ransomware campaigns is listed as unknown.
Does exploitation require user action?
Yes. The CVSS vector indicates user interaction is required and the attack vector is local, though no privileges are needed.
How do I know a system is fixed?
Check the OS build number. For example, Windows 11 version 21H2 is fixed at 10.0.22000.493 and Windows Server 2022 at 10.0.20348.524. Each affected version has its own fixed build in the record.

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.