CVE Tools

CVE-2026-59125

Virtual Hard Disk (VHD) Miniport Driver Elevation of Privilege Vulernability

No known exploitation. EPSS puts it in the 16th 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 Windows edition/version each device runs (Windows 10/11 or Windows Server 2016/2019/2022/2025) and identify your current build number.
  2. Compare your device build against the fixed versions from Microsoft for your specific Windows branch.
  3. Upgrade/patch any affected device to the Microsoft fixed build (listed by branch in the next section).
  4. If patching is delayed, restrict local access to devices and remove unneeded accounts with local login capability until updates are applied.
  5. After patching, verify the update installed successfully and review security logs for unusual activity around crashes or VHD-related operations.

What it is

From the CVE record

Use after free in Virtual Hard Disk (VHD) Miniport Driver allows an authorized attacker to elevate privileges locally.

In plain language

Written by AI from the record

CVE-2026-59125 is a Windows Virtual Hard Disk driver bug that can let a local attacker gain full system control without clicking anything; if you’re a typical small business user, it matters mainly if someone on your device already has low-level access, and you should apply the Microsoft fix as soon as possible.

CVE-2026-59125 is a local use-after-free privilege escalation in the Virtual Hard Disk (VHD) miniport driver that can allow an authenticated attacker with low privileges to execute code with elevated rights.

If you're affected

  • Full takeover of the server
  • Stealing or altering business data
  • Ransomware follow-on risk
  • Service disruption

Exploitation

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

EPSS16th
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.3% chance of exploitation activity in the next 30 days, which ranks it in the 16th percentile of scored CVEs.

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

Lifecycle

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

  1. Patch availablerecord updated
  2. OpenVAS check added
  3. Patch availablerecord updated, record updated
  4. Publishedweakness classified, att&ck mapped, 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