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

> An attacker can execute arbitrary code on Windows systems by exploiting a null pointer dereference in the Windows Runtime component.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 18 Aug 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Feb 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-58gj-2v59-wxcq

## What is CVE-2022-21971?

CVE-2022-21971 is a high-severity vulnerability in Microsoft Windows 10 1809, published on 9 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Windows Runtime Remote Code Execution Vulnerability

Weakness: CWE-824 (Access of Uninitialized Pointer)

## Which versions are affected by CVE-2022-21971?

It affects 9 products.


Products: Microsoft Windows 10 1809, Microsoft Windows 10 1909, Microsoft Windows 10 20h2, Microsoft Windows 10 21h1, Microsoft Windows 10 21h2, Microsoft Windows 11 21h2, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 20h2.

## How do I fix CVE-2022-21971?

No fix has been published for CVE-2022-21971 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 8 Sep 2022.

## Is CVE-2022-21971 being exploited?

Yes. Attackers have exploited CVE-2022-21971 in the wild since at least 18 Aug 2022.

Public exploit code:

- PoC for CVE-2022-21971 "Windows Runtime Remote Code Execution Vulnerability" (github_poc): https://github.com/0vercl0k/CVE-2022-21971
- POC Of CVE-2022-21971  (github_poc): https://github.com/Malwareman007/CVE-2022-21971
- https://github.com/tufanturhan/CVE-2022-21971-Windows-Runtime-RCE (github_poc): https://github.com/tufanturhan/CVE-2022-21971-Windows-Runtime-RCE

## Other vulnerabilities in Microsoft Windows 10 1809

- [CVE-2024-29988](https://insights.sbomify.com/CVE-2024-29988/): Microsoft SmartScreen Prompt Security Feature Bypass (high 8.8, exploited in the wild)
- [CVE-2024-21412](https://insights.sbomify.com/CVE-2024-21412/): Microsoft Windows Internet Shortcut Files Security Feature Bypass (high 8.1, exploited in the wild)
- [CVE-2025-62221](https://insights.sbomify.com/CVE-2025-62221/): Microsoft Windows Use After Free (high 7.8, exploited in the wild)
- [CVE-2025-30400](https://insights.sbomify.com/CVE-2025-30400/): Microsoft Windows DWM Core Library Use-After-Free (high 7.8, exploited in the wild)
- [CVE-2024-21338](https://insights.sbomify.com/CVE-2024-21338/): Microsoft Windows Kernel Exposed IOCTL with Insufficient Access Control (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-21971 and fix it if it is affected.

What it is: CVE-2022-21971 is a high-severity vulnerability in Microsoft Windows 10 1809, published on 9 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2022-21971 in the wild since at least 18 Aug 2022.

Affected product: Microsoft Windows 10 1809. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-21971/ (Markdown: https://insights.sbomify.com/CVE-2022-21971/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-21971
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-21971
- OSV: https://osv.dev/vulnerability/CVE-2022-21971

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-21971/
Summaries are generated and may contain mistakes; the official description above is the record.