Threats / Microsoft / CVE-2022-41125
CVE-2022-41125
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Microsoft Windows vulnerability
Microsoft Windows CNG Key Isolation Service vulnerability allows attackers to escalate privileges to SYSTEM level through an unspecified flaw in cryptographic key handling.
Verdict
Today item — known-exploited.
A privilege escalation vulnerability in Windows CNG Key Isolation Service enables local attackers to gain SYSTEM-level access. Active exploitation in the wild indicates immediate risk to Windows systems requiring prompt patching.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-11-08).
Probability (EPSS)
EPSS 0.03021 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I exploit a flaw in the CNG Key Isolation Service to escalate my local user privileges to SYSTEM level.
Business
Attackers gain unrestricted control over Windows systems, enabling installation of malware, data theft, and lateral movement across enterprise networks.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage SYSTEM access to disable security controls and persistence mechanisms on the compromised host.
Business
Security tools become ineffective, allowing attackers to maintain long-term presence and evade detection across the infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05