CVE-2023-36424: Windows Common Log File System privilege escalation

Quick Answer

CVE-2023-36424 is a local privilege-escalation flaw in the Windows Common Log File System driver. Microsoft's FAQ describes elevation from Medium to High Integrity Level, not a verified SYSTEM or root outcome. Identify the Windows branch and applicable current security update, preserve suspicious process and CLFS evidence, and use the historical mapping below only to establish fix lineage. CISA's 2026 KEV addition remains relevant even though Microsoft's 2023 record says Exploited: No.

Evidence check: The vendor evidence and its limits are described below. CISA KEV catalog 2026.10.02 was checked October 2; catalog chronology is separate from vendor publication history and evidence of compromise in your deployment. No exploit or update test is claimed.

Context

Status At A Glance

Product scope	Microsoft — Windows
CVE	CVE-2023-36424
TechGeeks response tier	P0 — confirm an exact match and act now
CISA KEV added	2026-04-13
Vendor severity	Important (Microsoft).
CVSS	7.8 (Microsoft CVSS v3.1 base; local, low privileges required).
Ransomware field	Unknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage field	No in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWE	CWE-125
Federal remediation date	2026-04-27 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

CLFS privilege escalation: CISA identifies an out-of-bounds read in the Common Log File System driver; Microsoft's FAQ specifies Medium-to-High integrity escalation. Known exploitation does not establish prevalence, a particular host's compromise or a more privileged outcome than the source describes.

Affected Scope

Windows releases and builds listed in the Microsoft advisory; the affected component is the Common Log File System driver.

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

1. Confirm. Inventory every Windows asset and record its exact version, patch level, role, relevant configuration, and exposure.
2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Microsoft advisory.
4. Remediate. Install the applicable Microsoft security update and verify the resulting Windows build against the live advisory.
5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Investigation And Recovery

The out-of-bounds read can support local privilege escalation. CISA added the CVE to KEV on 2026-04-13; review endpoint telemetry for abnormal CLFS-related crashes or privilege transitions.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: Microsoft's November 2023 record says Exploited: No. CISA subsequently added CVE-2023-36424 on April 13, 2026; do not treat that historical Microsoft assessment as a current no-exploitation claim.

CISA statement: CVE-2023-36424 was added to KEV on 2026-04-13. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

• TechGeeks Security Notice Center
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Microsoft security advisory
• Microsoft security advisory
• NVD CVE record
• CISA source

Wrap-Up

Record whether CVE-2023-36424 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.