dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 9 Dec 2022.
Windows 10 1507Operating system · Microsoft

CVE-2022-41125

HIGH · 7.8 CVSS v3.1 Published 2022-11-09
Fix available
A fix is available. Upgrade to 10.0.10240.19567 / 10.0.14393.5501 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windows CNG Key Isolation Service Elevation of Privilege Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Windows CNG Key Isolation Service contains an elevation of privilege vulnerability that allows a local attacker to gain higher system privileges. The CNG Key Isolation service runs with elevated privileges and improper access control could allow a low-privileged user to execute code in the context of the service account.

MitigationApply Microsoft security updates for CVE-2022-41125 or install the latest Windows cumulative security update. Prioritize patching systems with direct user access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.19567
Windows 10 1607Operating system
Affected:< 10.0.14393.5501
Windows 10 1809Operating system
Affected:< 10.0.17763.3650
Windows 10 20h2Operating system
Affected:< 10.0.19042.2251
Windows 10 21h1Operating system
Affected:< 10.0.19043.2251
Windows 10 21h2Operating system
Affected:< 10.0.19044.2251
Windows 10 22h2Operating system
Affected:< 10.0.19045.2251
Windows 11 21h2Operating system
Affected:< 10.0.22000.1219

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number
    Affected if The displayed build number falls below the thresholds: 10240.19567 (1507), 14393.5501 (1607), 17763.3650 (1809), 19042.2251 (20h2), 19043.2251 (21h1), 19044.2251 (21h2), 19045.2251 (22h2), or 22000.1219 (Windows 11 21h2)
  2. Verify CNG Key Isolation service status
    Open Services console (services.msc) or run 'sc query KeyIso' in Command Prompt to check if the CNG Key Isolation service (KeyIso) is present and running
    Affected if The KeyIso service exists and is running on a vulnerable Windows version (the service must be enabled for this vulnerability to be exploitable)
  3. Confirm detailed OS build via PowerShell
    Run 'Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" | Select-Object CurrentBuild, DisplayVersion, UBR' in PowerShell to get precise build and revision numbers
    Affected if The CurrentBuild and UBR values combined are lower than the specific patch version thresholds listed for your Windows release

You are affected if your Windows version is one of the listed releases AND your current build number is below the specified threshold, with the CNG Key Isolation service enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.19567 / 10.0.14393.5501 / 10.0.17763.3650 or later
Fixed in 10.0.10240.1956710.0.14393.550110.0.17763.3650
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply Microsoft security updates for CVE-2022-41125 or install the latest Windows cumulative security update. Prioritize patching systems with direct user access.

Recommended fix High confidence

Install the November 2022 Windows Security Update (KB5019959) or later for your Windows version

  1. Open Windows Settings on the affected system
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Ensure the system reboots after updates are installed
  5. Verify the installed version matches or exceeds the fixed build number for your Windows version: Windows 10 1507 should be 10.0.10240.19567 or later, Windows 10 1607 should be 10.0.14393.5501 or later, Windows 10 1809 should be 10.0.17763.3650 or later, Windows 10 20H2 should be 10.0.19042.2251 or later, Windows 10 21H1 should be 10.0.19043.2251 or later, Windows 10 21H2 should be 10.0.19044.2251
Caveat Standard Windows updateapply with minimal risk; ensure backups and compatibility testing for mission-critical systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41125 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41125 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data