CVE-2026-20805 remediation guide

Identify the affected asset

Confirm whether Microsoft Windows 10 Version 1607, Windows 10 Version 1809, Windows 10 Version 21H2 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.

Validate the affected-version match

Compare the deployed version with the affected range: >= 10.0.14393.0 < 10.0.14393.8783, >= 10.0.17763.0 < 10.0.17763.8276, >= 10.0.19044.0 < 10.0.19044.6809, >= 10.0.19045.0 < 10.0.19045.6809, >= 10.0.22631.0 < 10.0.22631.6491, >= 10.0.26100.0 < 10.0.26100.7623, >= 10.0.26200.0 < 10.0.26200.7623, >= 6.2.9200.0 < 6.2.9200.25868, >= 6.3.9600.0 < 6.3.9600.22968, >= 10.0.20348.0 < 10.0.20348.4648, >= 10.0.25398.0 < 10.0.25398.2092, >= 10.0.26100.0 < 10.0.26100.32230, < 10.0.14393.8783, < 10.0.17763.8276, < 10.0.19044.6809, < 10.0.19045.6809, < 10.0.22631.6491, < 10.0.26100.7623, < 10.0.26200.7623, r2. Treat incomplete inventory results as unresolved.

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.

Apply supported remediation

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

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.