dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32214

MEDIUM · 5.5 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 →
57/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
Improper access control in Universal Plug and Play (upnp.dll) allows an authorized attacker to disclose information 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

This is an improper access control vulnerability in the Universal Plug and Play component (upnp.dll). An authorized attacker with local access can exploit this to disclose sensitive information due to insufficient access restrictions within the UPnP service.

MitigationApply the relevant Microsoft security update for upnp.dll when available, or disable UPnP if not required, and verify that proper file system and service permissions are enforced.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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. Locate the upnp.dll file
    Open File Explorer and navigate to C:\Windows\System32\upnp.dll (or use command: dir C:\Windows\System32\upnp.dll)
    Affected if File does not exist (UPnP may not be installed)
  2. Check the installed version of upnp.dll
    Right-click upnp.dll, select Properties, go to the Details tab, and note the File Version value. Alternatively, run: powershell (Get-Item 'C:\Windows\System32\upnp.dll').VersionInfo.FileVersion
    Affected if The version number is lower than the fixed version for your Windows build (see affected version ranges)
  3. Identify your Windows build number
    Run winver or go to Settings > System > About and note the OS Build number
    Affected if Your build falls within one of the affected version ranges and the upnp.dll version is below the corresponding fixed version
  4. Check if UPnP service is running
    Open Services (services.msc) and look for 'UPnP Device Host' service status, or run: Get-Service | Where-Object {$_.Name -like '*UPnP*'}
    Affected if The UPnP service is running or set to Automatic start - the vulnerability requires the UPnP component to be active

You are affected if your Windows build matches an affected version range AND your upnp.dll version is below the fixed version threshold AND the UPnP service is enabled or running.

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 the relevant Microsoft security update for upnp.dll when available, or disable UPnP if not required, and verify that proper file system and service permissions are enforced.

Recommended fix High confidence

Windows 10 1607 build 10.0.14393.9060 or later; Windows 10 1809 build 10.0.17763.8644 or later; Windows 10 21h2 build 10.0.19044.7184 or later; Windows 10 22h2 build 10.0.19045.7184 or later; Windows 11 23h2 build 10.0.22631.6936 or later; Windows 11 24h2 build 10.0.26100.8246 or later; Windows 11 2

  1. Open Settings > System > About to check your current Windows build number
  2. Note your current Windows version and build (e.g., Windows 10 22h2, build 19045.xxxx)
  3. Open Windows Update (Settings > Update & Security > Windows Update)
  4. Click 'Check for updates' and install all available updates
  5. After updates complete, restart your computer
  6. Verify the installed build meets or exceeds: 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
  7. If automatic updates do not provide the required build, manually download and install the specific Cumulative Update KB from Microsoft Update Catalog for your Windows version

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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