dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-26156

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.14393.9060 / 10.0.17763.8644 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Heap-based buffer overflow in Windows Hyper-V allows an unauthorized attacker to execute code 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 confidence

Heap-based buffer overflow vulnerability in Windows Hyper-V allows a local attacker to execute arbitrary code. This is a memory corruption flaw in the hypervisor's components that can be exploited by an unauthenticated user with local access to the system.

MitigationApply Microsoft security updates for Windows Hyper-V when available. Restrict physical and logical access toHyper-V host systems to trusted only.

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
Windows 10 1607Operating system
Affected:< 10.0.14393.9060
Windows 10 1809Operating system
Affected:< 10.0.17763.8644
Windows 10 21h2Operating system
Affected:< 10.0.19044.7184
Windows 10 22h2Operating system
Affected:< 10.0.19045.7184
Windows 11 23h2Operating system
Affected:< 10.0.22631.6936
Windows 11 24h2Operating system
Affected:< 10.0.26100.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246
Windows 11 26h1Operating system
Affected:< 10.0.28000.1836

CVSS 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Hyper-V hypervisor is enabled
    Run 'systeminfo' or 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All' in PowerShell. Check the Hyper-V section in systeminfo output.
    Affected if Hyper-V is listed as enabled or installed on the system.
  2. Confirm Windows build version
    Run 'winver' or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the full Windows build number.
    Affected if The build version matches any of the affected version ranges listed in the CVE (below 10.0.14393.9060 for 1607, below 10.0.17763.8644 for 1809, below 10.0.19044.7184 for 21h2, below 10.0.19045.7184 for 22h2, below 10.0.22631.6936 for 23h2, below 10.0.26100.8246 for 24h2, below 10.0.26200.8246 for 25
  3. Check exact build number via registry
    Query the registry using 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuildNumber' and '/v DisplayVersion' if available.
    Affected if The CurrentBuildNumber value is lower than the fixed build for your specific Windows release channel.

The system is affected if Hyper-V is enabled and the Windows build version falls below the specified threshold for your Windows release.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.14393.9060 / 10.0.17763.8644 / 10.0.19044.7184 or later
Fixed in 10.0.14393.906010.0.17763.864410.0.19044.7184
Interim mitigation

Apply Microsoft security updates for Windows Hyper-V when available. Restrict physical and logical access toHyper-V host systems to trusted only.

Recommended fix High confidence

Apply Microsoft security update for CVE-2026-2616; minimum fixed builds: Windows 10 1607 to 10.0.14393.9060, Windows 10 1809 to 10.0.17763.8644, Windows 10 21h2 to 10.0.19044.7184, Windows 10 22h2 to 10.0.19045.7184, Windows 11 23h2 to 10.0.22631.6936, Windows 11 24h2 to 10.0.26100.8246, Windows 11

  1. Check current Windows build version by running 'winver' or 'systeminfo' to confirm the installed version
  2. Open Windows Update (Settings > Update & Security > Windows Update) and check for updates
  3. Apply the relevant Microsoft security update for CVE-2026-26156 from the Microsoft Security Update Guide (msrc.microsoft.com)
  4. Alternatively, manually download and install the specific security update for your Windows version from the Microsoft Update Catalog
  5. Restart the system after applying the update
  6. Verify the update was installed successfully by checking the installed updates list or running 'winver' to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update applies; ensure backups of critical VMs and data exist before updating production Hyper-V hosts

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26156 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26156 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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