dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32075

HIGH · 7.0 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 →
72/100
Remediation priority · Elevated
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 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 · low confidence

Use-after-free vulnerability in Windows Universal Plug and Play (UPnP) Device Host enables a local authorized attacker to escalate privileges to higher integrity levels.

MitigationApply Microsoft security updates for Windows UPnP Device Host once released; restrict local access to trusted users to reduce attack surface.

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

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

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

  1. Identify Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the full Windows version and build number
    Affected if The build number falls below any of the following thresholds: 14393.9060, 17763.8644, 19044.7184, 19045.7184, 22631.6936, 26100.8246, 26200.8246, or 28000.1836 depending on your Windows release
  2. Verify UPnP Device Host component is present
    Check for the presence of the UPnP Device Host service by running 'sc query UPNPHOST' or inspecting 'C:\Windows\System32\upnphost.dll'
    Affected if The UPnP Device Host service or binary exists on the system, indicating the vulnerable component is installed
  3. Confirm UPnP Device Host service status
    Run 'sc queryex type= service state= all' and search for 'upnphost' or check the service via Services.msc
    Affected if The UPnP Device Host service is present in the services list, regardless of running state, as the vulnerability exists in the component itself
  4. Compare installed build against CVE version thresholds
    Obtain the exact build number via 'winver' or 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and cross-reference with the vulnerable version ranges listed in the CVE
    Affected if Your installed build number is lower than the fixed version for your specific Windows release as enumerated in the CVE affected products list

You are affected if your Windows build number is below the threshold for your specific Windows release AND the UPnP Device Host component exists on your system.

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 UPnP Device Host once released; restrict local access to trusted users to reduce attack surface.

Recommended fix High confidence

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

  1. Identify your current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows version category you are on (10 1607, 10 1809, 10 21h2, 10 22h2, 11 23h2, 11 24h2, 11 25h2, or 11 26h1)
  3. Open Windows Update by going to Settings > Update & Security > Windows Update
  4. Click 'Check for updates' and install all available security updates
  5. Alternatively, manually download the appropriate cumulative update from the Microsoft Update Catalog: https://www.catalog.update.microsoft.com/
  6. After installation, restart your computer to apply the security patch
  7. Verify the installed build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows cumulative update apply; may require restart; no major functional changes expected for this security-only update

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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