Windows VHD Miniport is a core OS driver used broadly; a high-severity privilege escalation in Windows affects most enterprises and warrants org-wide attention.
CVE-2026-69681
Heap overflow in Windows VHD Miniport Driver enabling privilege escalation.
Is CVE-2026-69681 being exploited?
Not confirmed. CVE-2026-69681 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.77% probability of exploitation in the next 30 days.
How severe is CVE-2026-69681?
CVE-2026-69681 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-69681?
Yes. A fix has been recorded for CVE-2026-69681. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-69681 affect?
CVE-2026-69681 affects Microsoft Windows VHD Miniport Driver, Windows desktop and server editions (per vendor advisory). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-69681?
Apply Microsoft security update immediately and reboot affected hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can trigger heap-based overflow in VHD Miniport to elevate privileges to SYSTEM, fully compromising host.
Immediate action required
- affected>= 10.0.14393.0 and < 10.0.14393.9512
- affected>= 10.0.17763.0 and < 10.0.17763.9245
- affected>= 10.0.19044.0 and < 10.0.19044.7725
- affected>= 10.0.19045.0 and < 10.0.19045.7725
- affected>= 10.0.22631.0 and < 10.0.22631.7582
- affected>= 10.0.22631.0 and < 10.0.22631.7582
- affected>= 10.0.26100.0 and < 10.0.26100.9445
- affected>= 10.0.26200.0 and < 10.0.26200.9445
- affected>= 10.0.28000.0 and < 10.0.28000.2954
- affected>= 6.2.9200.0 and < 6.2.9200.26349
- affected>= 6.3.9600.0 and < 6.3.9600.23397
- affected>= 6.3.9600.0 and < 6.3.9600.23397
- affected>= 6.2.9200.0 and < 6.2.9200.26349
- affected>= 10.0.14393.0 and < 10.0.14393.9512
- affected>= 10.0.14393.0 and < 10.0.14393.9512
- affected>= 10.0.17763.0 and < 10.0.17763.9245
- affected>= 10.0.17763.0 and < 10.0.17763.9245
- affected>= 10.0.20348.0 and < 10.0.20348.5622
- affected>= 10.0.26100.0 and < 10.0.26100.33438
- affected>= 10.0.26100.0 and < 10.0.26100.33438
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.