CVE-2022-41125

Windows CNG Key Isolation Service Elevation of Privilege Vulnerability

HIGH
7.8
CVSS Score
Published: November 9, 2022 at 12:00 AM UTC
Updated: August 10, 2026 at 04:28 PM UTC
14 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploitation
CISA KEV
Exploit prediction
EPSS 3%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score3.0%

EPSS (Exploit Prediction Scoring System) estimates a 3.0% chance this CVE is exploited in the wild within the next 30 days — higher than 87% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Microsoft Windows Cryptographic Next Generation (CNG) Key Isolation Service contains an unspecified vulnerability that allows an attacker to gain SYSTEM-level privileges.

Required Action
Apply updates per vendor instructions.
Ransomware Use
Unknown
Added to KEV
Nov 8, 2022
Remediation Due
Dec 9, 2022
1419 days overdue

Description

Windows CNG Key Isolation Service Elevation of Privilege Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.10240.1956710.0.10240.0 ≤ v < 10.0.10240.1956710.0.10240.0
Affected range stops below 10.0.10240.19567, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.550110.0.14393.0 ≤ v < 10.0.14393.550110.0.14393.0
Affected range stops below 10.0.14393.5501, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.365010.0.0 ≤ v < 10.0.17763.365010.0.17763.0 ≤ v < 10.0.17763.365010.0.010.0.17763.0
Affected range stops below 10.0.17763.3650, so it looks safe — our inference, not a vendor statement
v < 10.0.19042.225110.0.0 ≤ v < 10.0.19042.225110.0.0
Affected range stops below 10.0.19042.2251, so it looks safe — our inference, not a vendor statement
v < 10.0.19043.225110.0.0 ≤ v < 10.0.19043.225110.0.0
Affected range stops below 10.0.19043.2251, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.225110.0.19043.0 ≤ v < 10.0.19044.225110.0.19043.0
Affected range stops below 10.0.19044.2251, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.225110.0.19045.0 ≤ v < 10.0.19045.225110.0.19045.0
Affected range stops below 10.0.19045.2251, so it looks safe — our inference, not a vendor statement
v < 10.0.22000.121910.0.0 ≤ v < 10.0.22000.121910.0.0
Affected range stops below 10.0.22000.1219, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.81910.0.22621.0 ≤ v < 10.0.22621.81910.0.22621.0
Affected range stops below 10.0.22621.819, so it looks safe — our inference, not a vendor statement
6.3.0 ≤ v < 6.3.9600.206716.3.0
Affected range stops below 6.3.9600.20671, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card