CVE Tools

CVE-2026-62728

Windows Common Log File System Driver Elevation of Privilege Vulnerability

No known exploitation. EPSS puts it in the 9th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check which of these are installed and their OS version: Windows 10, Windows 11, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows Server 2025.
  2. Verify whether the machine is already updated past these fixed build numbers for your specific Windows version.
  3. Install the Microsoft security update for CVE-2026-62728 from the MSRC update guide.
  4. If you can’t patch immediately, restrict or remove low-privilege accounts that are able to log on to the affected systems, and monitor for unusual privilege changes and suspicious activity around file system actions by non-admin users.

What it is

From the CVE record

Time-of-check time-of-use (toctou) race condition in Windows Common Log File System Driver allows an authorized attacker to elevate privileges locally.

In plain language

Written by AI from the record

CVE-2026-62728 is a Windows local security bug that lets a normal logged-in user exploit a timing flaw to gain administrator control; if your business has Windows machines with standard user accounts, you should patch.

CVE-2026-62728 is a local privilege escalation due to a time-of-check time-of-use (TOCTOU) race condition in the Windows Common Log File System Driver, where an attacker with a low-privilege account can change a file between the driver’s checks and later use to trick it into granting higher-level access.

If you're affected

  • Full admin control by insiders
  • Malware persistence with admin rights
  • Total compromise of business systems
  • High operational disruption risk

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS9th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 9th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

12 events over 5 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. OpenVAS check addedpatch available, record updated
  3. Record updatedrecord updated
  4. Publishedweakness classified, att&ck mapped, record updated, record updated

Affected products

Technical detail

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

Scored 7.0 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Windows 10 Version 1607, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store