CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighFixed-version data available

CVE-2022-41128 remediation guide

Microsoft Windows

CVE-2022-41128 affects Microsoft Windows. Review the CVSS score, exploitation signals, affected versions, remediation status, and linked source material before making a change.

Open CVE record
ProductMicrosoft Windows
Affected versions10.0.17763.0, 10.0.0, 10.0.20348.0, 10.0.19043.0, 10.0.22621.0, 10.0.19045.0, 10.0.10240.0, 10.0.14393.0, 6.1.0, 6.3.0, 6.1.7601.0, 6.2.9200.0, 6.3.9600.0, < 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
Fixed versions10.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, 10.0.20348.1249
Priority basisImmediate · CVSS 8.8 · EPSS 24.6%
01

Identify the affected asset

Confirm whether Microsoft Windows is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 10.0.17763.0, 10.0.0, 10.0.20348.0, 10.0.19043.0, 10.0.22621.0, 10.0.19045.0, 10.0.10240.0, 10.0.14393.0, 6.1.0, 6.3.0, 6.1.7601.0, 6.2.9200.0, 6.3.9600.0, < 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. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.