dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32149

HIGH · 7.3 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 →
73/100
Remediation priority · Elevated

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
Improper input validation in Windows Hyper-V allows an authorized 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

Improper input validation vulnerability in Windows Hyper-V allows an authorized attacker to execute arbitrary code locally on the host system through the hypervisor layer.

MitigationApply Microsoft security updates for Windows Hyper-V when released; ensure authorized user privileges are scoped to minimum necessary for operational requirements.

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Confirm Hyper-V is enabled
    Run 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' in PowerShell or check 'systeminfo' for Hyper-V requirements
    Affected if Hyper-V is installed and enabled on the system
  2. Identify Windows build version
    Run 'winver' or 'Get-ComputerInfo | Select-Object OsVersion, OsBuildNumber' in PowerShell to get the exact build number
    Affected if The displayed build number falls below the threshold for your specific Windows release (e.g., for Windows 10 22h2: below 10.0.19045.7184)
  3. Map build to release version
    Cross-reference the build number with known Windows release versions (e.g., 19045 = Windows 10 22h2, 22631 = Windows 11 23h2, 26100 = Windows 11 24h2)
    Affected if The identified release version and build combination is listed in the affected versions range

You are affected if Hyper-V is enabled AND your Windows build version is lower than the specific threshold for your Windows release version.

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 released; ensure authorized user privileges are scoped to minimum necessary for operational requirements.

Recommended fix High confidence

Apply the corresponding security update for your Windows version: Windows 10 1607 to build 10.0.14393.9060, Windows 10 1809 to build 10.0.17763.8644, Windows 10 21h2 to build 10.0.19044.7184, Windows 10 22h2 to build 10.0.19045.7184, Windows 11 23h2 to build 10.0.22631.6936, Windows 11 24h2 to build

  1. 1. Identify the Windows version and build currently installed by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which version bracket your system falls into (Windows 10 1607, 1809, 21h2, 22h2, or Windows 11 23h2, 24h2, 25h2, 26h1)
  3. 3. Open Windows Update by going to Settings > Update & Security > Windows Update
  4. 4. Click 'Check for updates' to download and install the latest security updates
  5. 5. Alternatively, manually download the appropriate security update from the Microsoft Update Catalog (search for the KB number corresponding to CVE-2026-32149 on msrc.microsoft.com)
  6. 6. After installation, restart the computer when prompted
  7. 7. Verify the fix by checking that the installed build matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update with no expected breaking changes; as a local privilege escalation rather than remote, impact is limited to authorized local attackers

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
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32149 — 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-32149 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