dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32212

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 link resolution before file access ('link following') 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 a symlink/hardlink following vulnerability in the Universal Plug and Play service (upnp.dll). An authorized local attacker could exploit improper link resolution to access sensitive files they wouldn't normally have permission to read, leading to local information disclosure.

MitigationApply vendor patches when available; restrict file system permissions on directories used by the UPnP service; consider disabling UPnP if not required in the environment.

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. Verify if UPnP service is running
    Open Services (services.msc) and look for 'UPnP Device Host' service, or run 'Get-Service upnphost' in PowerShell
    Affected if The UPnP service is present and running (status shows 'Running')
  2. Locate and check upnp.dll version
    Find upnp.dll in System32 folder (typically C:\Windows\System32\upnp.dll), right-click and view Properties > Details to see File Version
    Affected if The file version shown is lower than the patched version for your Windows build (compare against the version thresholds in the CVE advisory)
  3. Confirm Windows build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the exact Windows build (e.g., 14393, 17763, 19044, etc.)
    Affected if The build number falls below the patched threshold for your Windows version (10.0.14393.9060 for 1607, 10.0.17763.8644 for 1809, etc.)

You are affected if the UPnP service is enabled and either your upnp.dll version or Windows build is below the patched version for your specific 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 vendor patches when available; restrict file system permissions on directories used by the UPnP service; consider disabling UPnP if not required in the environment.

Recommended fix High confidence

Apply the appropriate Microsoft Security Update for CVE-2026-32212 via Windows Update or manual KB download - the fixed builds are listed in the affected versions (e.g., 10.0.14393.9060 and выше)

  1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo'
  2. Open Windows Settings > Update & Security > Windows Update
  3. Check for updates and install all available updates, or manually download the specific KB for this CVE from the Microsoft Update Catalog
  4. For enterprise deployments, use Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager to deploy the security update
  5. After installation, verify the upnp.dll version matches or exceeds the fixed build: 10.0.14393.9060 (1607), 10.0.17763.8644 (1809), 10.0.19044.7184 (21h2), 10.0.19045.7184 (22h2), 10.0.22631.6936 (23h2), 10.0.26100.8246 (24h2), 10.0.26200.8246 (25h2), or 10.0.28000.1836 (26h1)
  6. Restart the affected system to ensure the patched upnp.dll is loaded
Caveat None expected - this is a routine security patch for a local information disclosure vulnerability in the UPnP component

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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