dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32156

HIGH · 7.4 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 →
79/100
Remediation priority · High
No privileges Zero-click

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
Use after free in Windows Universal Plug and Play (UPnP) Device Host 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

A use-after-free vulnerability in the Windows Universal Plug and Play (UPnP) Device Host service allows a local attacker to execute arbitrary code by referencing freed memory, potentially achieving code execution with service-level privileges.

MitigationApply Microsoft security updates for Windows when released. If immediate patching is not possible, consider disabling the UPnP Device Host service if business functionality does not require it.

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

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

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

  1. Verify UPnP Device Host service status
    Open Services (services.msc) or run 'Get-Service upnphost' in PowerShell to check if the UPnP Device Host service is installed and its current running state
    Affected if The service is running (even if manually started) - the vulnerability requires the service to be active for exploitation
  2. Confirm Windows version is within affected range
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the exact Windows build number
    Affected if The installed Windows version matches any of the affected versions listed (10.0.14393.xxxx through 10.0.28000.xxxx, below the specified patch thresholds)
  3. Compare build number to patch threshold
    Run 'ver' at command prompt or check the Windows version details; compare the full build number (e.g., 10.0.19045.7181) against the minimum fixed version for your specific Windows release
    Affected if The installed build number is lower than the threshold for your Windows version (e.g., 19045.7184 for 10 22h2, 22631.6936 for 11 23h2, etc.)

The system is affected if the UPnP Device Host service is running AND the Windows build number is below the patch threshold for that specific Windows 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 when released. If immediate patching is not possible, consider disabling the UPnP Device Host service if business functionality does not require it.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.9060 | Windows 10 1809: build 10.0.17763.8644 | Windows 10 21h2: build 10.0.19044.7184 | Windows 10 22h2: build 10.0.19045.7184 | Windows 11 23h2: build 10.0.22631.6936 | Windows 11 24h2: build 10.0.26100.8246 | Windows 11 25h2: build 10.0.26200.8246 | Windows 11 26

  1. 1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. 2. Navigate to Windows Update: Settings > Update & Security > Windows Update
  3. 3. Click 'Check for updates' to download and install the latest security updates
  4. 4. Alternatively, download the specific security update from Microsoft Update Catalog for your Windows version
  5. 5. Restart the system after updates are installed
  6. 6. Verify the build number has been updated to the fixed version or later
Caveat Standard Windows security update; no breaking changes expected for typical deployments

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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