# CVE-2022-21882: Microsoft Win32k Privilege Escalation

> An attacker can exploit a memory corruption flaw in the Windows kernel to gain elevated privileges on affected systems.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 4 Feb 2022 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2022
- **Updated:** 15 Aug 2026
- **Also known as:** GHSA-m3vx-53cf-jqv4

## What is CVE-2022-21882?

CVE-2022-21882 is a high-severity memory corruption vulnerability in Microsoft Windows 10 1809, published on 11 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Win32k Elevation of Privilege Vulnerability

Weakness: CWE-787 (Out-of-bounds Write)

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

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-21882?

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

## Is CVE-2022-21882 being exploited?

Yes. Attackers have exploited CVE-2022-21882 in the wild since at least 4 Feb 2022, including in ransomware campaigns.

Public exploit code:

- win32k LPE  (github_poc): https://github.com/KaLendsi/CVE-2022-21882
- https://github.com/L4ys/CVE-2022-21882 (github_poc): https://github.com/L4ys/CVE-2022-21882
- lpe poc for cve-2022-21882  (github_poc): https://github.com/sailay1996/cve-2022-21882-poc
- CVE-2022-21882 (github_poc): https://github.com/David-Honisch/CVE-2022-21882
- https://github.com/r1l4-i3pur1l4/CVE-2022-21882 (github_poc): https://github.com/r1l4-i3pur1l4/CVE-2022-21882
- Win32k ConsoleControl Offset Confusion (metasploit)

## 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-21882 and fix it if it is affected.

What it is: CVE-2022-21882 is a high-severity memory corruption vulnerability in Microsoft Windows 10 1809, published on 11 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-21882 in the wild since at least 4 Feb 2022, including in ransomware campaigns.

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-21882/ (Markdown: https://insights.sbomify.com/CVE-2022-21882/index.md)
```

## Sources

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

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