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

CVE-2021-36934 remediation guide

Microsoft Windows

<p>An elevation of privilege vulnerability exists because of overly permissive Access Control Lists (ACLs) on multiple system files, including the Security Accounts Manager (SAM) database. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.</p> <p>An attacker must have the ability to execute code on a victim system to exploit this vulnerability.</p> <p>After installing this security update, you <em>must</em> manually dele...

Open CVE record
ProductMicrosoft Windows
Affected versions10.0.0, < 10.0.17763.2114, < 10.0.18363.1734, < 10.0.19041.1165, < 10.0.19042.1165, < 10.0.19043.1165
Fixed versions10.0.17763.2114, 10.0.18363.1734, 10.0.19041.1165, 10.0.19042.1165, 10.0.19043.1165
Priority basisImmediate · CVSS 7.8 · EPSS 67.3%
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.0, < 10.0.17763.2114, < 10.0.18363.1734, < 10.0.19041.1165, < 10.0.19042.1165, < 10.0.19043.1165. 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.