CVE-2022-21971
Microsoft Windows Runtime Remote Code Execution
- Published9 Feb 2022
- Added to CISA KEV18 Aug 2022
- Remediation due8 Sept 2022
Description
Windows Runtime Remote Code Execution Vulnerability
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2022-21971 being actively exploited?
Yes. CVE-2022-21971 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 18 Aug 2022.
How severe is CVE-2022-21971?
CVE-2022-21971 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 53.9% probability of exploitation.
Which products are affected by CVE-2022-21971?
Affected products include Microsoft Windows 10 1809, Microsoft Windows 10 1909, Microsoft Windows 10 20h2, Microsoft Windows 10 21h1, Microsoft Windows 10 21h2, and 4 more.
How do I fix CVE-2022-21971?
Upgrade affected software to a fixed version, for example Microsoft Windows 10 1809 10.0.17763.2565, Microsoft Windows 10 1909 10.0.18363.2094, Microsoft Windows 10 20h2 10.0.19042.1526 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2022-21971 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.