CVE-2022-41125: Microsoft Windows CNG Key Isolation Service Privilege Escalation
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-11-08.
- CVSS v3.1 (CVE record)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 3.0%
- higher than 87.8% of all CVEs
- Added to CISA KEV
- 2022-11-08
- US federal due date 2022-12-09
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2022-41125 explained
CVE-2022-41125 is a privilege escalation vulnerability in the Cryptographic Next Generation (CNG) Key Isolation Service of Microsoft Windows. It is an out-of-bounds write that lets an attacker gain SYSTEM-level privileges. CISA lists it as known exploited, so affected systems should be patched with priority.
Impact
An attacker who can already run code on a system with low privileges can raise those privileges to SYSTEM. No user interaction is needed and attack complexity is low. Successful exploitation gives high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected system. CISA rates it as not automatable, so it is not exploitable at scale without manual steps. Attackers are known to use it.
Who is affected
The CVE record lists Windows 10 (1507, 1607, 1809, 20H2, 21H1, 21H2, 22H2), Windows 11 (21H2, 22H2), Windows 8.1, and Windows Server 2012, including Server Core. Fixed builds include 10.0.10240.19567, 10.0.14393.5501, 10.0.17763.3650, 10.0.19042.2251, 10.0.19043.2251, 10.0.19044.2251, 10.0.19045.2251, 10.0.22000.1219, 10.0.22621.819, 6.3.9600.20671 and 6.2.9200.23968. Earlier builds of each version are affected. The page lists further products.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft Windows Cryptographic Next Generation (CNG) Key Isolation Service contains an unspecified vulnerability that allows an attacker to gain SYSTEM-level privileges.
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 150732-bit, x64AffectedFixed in
- < 10.0.10240.19567
- 10.0.10240.19567
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.5501
- 10.0.14393.5501
- Microsoft Windows 10 Version 180932-bit, x64, ARM64AffectedFixed in
- < 10.0.17763.3650
- 10.0.17763.3650
- Microsoft Windows 10 Version 20H232-bit, ARM64AffectedFixed in
- < 10.0.19042.2251
- 10.0.19042.2251
- Microsoft Windows 10 Version 21H132-bit, ARM64, x64AffectedFixed in
- < 10.0.19043.2251
- 10.0.19043.2251
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.2251
- 10.0.19044.2251
- Microsoft Windows 10 Version 22H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19045.2251
- 10.0.19045.2251
- Microsoft Windows 11 version 21H2ARM64, x64AffectedFixed in
- < 10.0.22000.1219
- 10.0.22000.1219
- Microsoft Windows 11 version 22H2ARM64, x64AffectedFixed in
- < 10.0.22621.819
- 10.0.22621.819
- Microsoft Windows 8.132-bit, ARM64, x64AffectedFixed in
- < 6.3.9600.20671
- 6.3.9600.20671
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 150732-bit, x64 |
|
|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows 10 Version 180932-bit, x64, ARM64 |
|
|
| Microsoft Windows 10 Version 20H232-bit, ARM64 |
|
|
| Microsoft Windows 10 Version 21H132-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 21H2ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H2ARM64, x64 |
|
|
| Microsoft Windows 8.132-bit, ARM64, x64 |
|
|
Show 9 more products
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.23968
- 6.2.9200.23968
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- < 6.2.9200.23968
- 6.2.9200.23968
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.20671
- 6.3.9600.20671
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- < 6.3.9600.20671
- 6.3.9600.20671
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.5501
- 10.0.14393.5501
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.5501
- 10.0.14393.5501
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.3650
- 10.0.17763.3650
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.3650
- 10.0.17763.3650
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.1249
- 10.0.20348.1249
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows Server 2012x64 |
|
|
| Microsoft Windows Server 2012 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012 R2x64 |
|
|
| Microsoft Windows Server 2012 R2 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1507: 10.0.10240.19567
- Microsoft Windows 10 Version 1607: 10.0.14393.5501
- Microsoft Windows 10 Version 1809: 10.0.17763.3650
- Microsoft Windows 10 Version 20H2: 10.0.19042.2251
- Microsoft Windows 10 Version 21H1: 10.0.19043.2251
- Microsoft Windows 10 Version 21H2: 10.0.19044.2251
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41125
- CISA's deadline for US federal agencies: 2022-12-09 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply Microsoft's security update for CVE-2022-41125 on all affected Windows systems, as CISA's required action states.
- Confirm each system runs at least the fixed build for its version, such as
10.0.19045.2251for Windows 10 Version 22H2. - Prioritize multi-user systems and servers where untrusted or low-privileged users can run code.
- Limit local and interactive access to trusted accounts to reduce who can attempt privilege escalation.
- Check unpatched systems for signs of compromise, such as unexpected SYSTEM-level processes or new privileged accounts.
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-787 Out-of-bounds Write
Questions about CVE-2022-41125
- Is CVE-2022-41125 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-11-08, with a due date of 2022-12-09 for US federal agencies. Whether it is used in ransomware campaigns is unknown.
- Can it be exploited remotely?
- The attack vector is local. An attacker needs low-privileged access to the system first and then uses this flaw to gain SYSTEM privileges.
- How do I fix it?
- Install Microsoft's security update for your Windows version. The CVE record names a fixed build for each listed version, for example
10.0.22621.819for Windows 11 version 22H2.
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-22. Always confirm with the vendor's or distribution's advisory before patching.