CVE-2025-26688
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 · uneditedStack-based buffer overflow in Microsoft Virtual Hard Drive allows an authorized attacker to elevate privileges locally.
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 confidenceA stack-based buffer overflow vulnerability exists in Microsoft Virtual Hard Drive that allows a local, authorized attacker to elevate privileges. The flaw occurs when the Virtual Hard Drive component improperly handles memory on the stack, enabling an attacker with local access to execute arbitrary code with elevated permissions.
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.10240.20978< 10.0.14393.7969< 10.0.17763.7136< 10.0.19044.5737< 10.0.19045.5737< 10.0.22621.5189< 10.0.22631.5189< 10.0.26100.3775CVSS 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 your Windows versionRun 'winver' from the Start menu or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt. Compare the build number to the affected ranges: 1507 (<10.0.10240.20978), 1607 (<10.0.14393.7969), 1809 (<10.0.17763.7136), 21h2 (<10.0.19044.5737), 22h2 (<10.0.19045.5737), 11 22h2 (<10.0.22621.5189), 11 23h2 (<10.0.22631.5189), 11 24h2 (<10.0.26100.3775)Affected if Your Windows build number falls below the version threshold for your specific Windows release (10 or 11, and its specific version/feature update)
-
Verify Virtual Hard Drive component is presentCheck for the presence of VHD mounting capability by opening Disk Management (diskmgmt.msc) or try mounting a VHDX file via PowerShell command 'Mount-VHD -Path test.vhdx -ErrorAction SilentlyContinue' if you have a test VHD file availableAffected if The system can mount VHD or VHDX virtual hard disk images, indicating the Virtual Hard Drive component is installed and functional
-
Confirm VHD-related system files existInspect the Windows VHD system files. Check for the existence of %SystemRoot%\System32\drivers\vhd.sys or search for vhd*.sys in the drivers directory using 'dir %SystemRoot%\System32\drivers\vhd*'Affected if VHD system driver files are present on the system, confirming the vulnerable component is installed
You are affected if your Windows version is below the threshold for your specific Windows release AND the Virtual Hard Drive component is present and functional on your system.
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.
dbcve · scoped10.0.10240.2097810.0.14393.796910.0.17763.7136
Apply the Microsoft security update for CVE-2025-26688 via Windows Update or Microsoft Update Catalog. Prioritize patching systems where untrusted users have local access, as this is a local privilege escalation vulnerability.
Upgrade to the latest Windows security update containing the CVE-2025-26688 patch; for each affected release, install the update that brings the build to: Windows 10 1507 (10.0.10240.20978+), Windows 10 1607 (10.0.14393.7969+), Windows 10 1809 (10.0.17763.7136+), Windows 10 21h2 (10.0.19044.5737+),
- Open Windows Settings and navigate to Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest security updates
- Alternatively, manually update by downloading the specific KB from Microsoft Update Catalog for your Windows version
- Restart the system after updates are installed
- Verify the update was successful by checking the installed updates (run 'appwiz.cpl' and view installed updates)
- Confirm the build number matches or exceeds the fixed version for your Windows release (e.g., for Windows 10 22h2, verify build >= 10.0.19045.5737)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26688 — 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-2025-26688 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