CVE-2026-58601
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHeap-based buffer overflow in Virtual Hard Disk (VHD) Miniport Driver allows an authorized attacker to elevate privileges locally.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceHeap-based buffer overflow in Windows Virtual Hard Disk (VHD) Miniport Driver allows a local authorized attacker to execute code with elevated (kernel) privileges by overflowing a heap-allocated buffer in the driver.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.0.14393.9339< 10.0.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.22631.7376< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2525CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Windows version against affected buildsRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' and compare the build number to the affected ranges (Windows 10 1607 < 14393.9339, 1809 < 17763.9020, 21h2 < 19044.7548, 22h2 < 19045.7548; Windows 11 23h2 < 22631.7376, 24h2 < 26100.8875, 25h2 < 26200.8875, 26h1 < 28000.2525)Affected if The installed build number falls within any of the vulnerable version ranges listed
-
Verify VHD Miniport Driver is loadedRun 'driverquery /v | findstr -i vhd' or check the driver status via 'sc query vhd' to determine if the Virtual Hard Disk Miniport driver is currently loaded in memoryAffected if The VHD Miniport Driver is loaded and the Windows version is in the affected range
-
Check for recent VHD mounting activityReview Windows Event Logs (Microsoft-Windows-VHDMP-Operational) or use 'mountvol' to list currently mounted VHD files, and check for any VHD mounting operationsAffected if VHD mounting has occurred on a system running a vulnerable Windows version with the driver loaded
A system is affected if it runs any Windows version within the specified build ranges AND has the VHD Miniport Driver loaded or in use
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data10.0.14393.933910.0.17763.902010.0.19044.7548
Apply the appropriate Windows security update for the VHD Miniport Driver when released; until then, limit local access to trusted users only and monitor for suspicious VHD mounting activity.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58601 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58601 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data