dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50455

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 5 weeks old

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 of uninitialized resource in Universal Plug and Play (upnp.dll) allows an authorized attacker to disclose information locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

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

An information disclosure vulnerability exists in Universal Plug and Play (upnp.dll) where an uninitialized resource is used, allowing a locally authenticated attacker to potentially read sensitive information from memory.

MitigationApply the relevant Microsoft security patch for this vulnerability when released. If UPnP is not required, consider disabling the service 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.9339
Windows 10 1809Operating system
Affected:< 10.0.17763.9020
Windows 10 21h2Operating system
Affected:< 10.0.19044.7548
Windows 10 22h2Operating system
Affected:< 10.0.19045.7548
Windows 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269< 10.0.28000.2525
Windows Server 2012Operating system
Affected:all versions= r2

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. Check Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build number
    Affected if The Windows build number is lower than the affected version for your Windows release (e.g., < 10.0.14393.9339 for Windows 10 1607, < 10.0.17763.9020 for Windows 10 1809, etc.)
  2. Verify upnp.dll presence
    Check if %SystemRoot%\System32\upnp.dll exists on the system using 'dir %SystemRoot%\System32\upnp.dll'
    Affected if The file exists on the system (vulnerability resides in this DLL)
  3. Check UPnP service status
    Run 'sc query upnphost' or check Services console for 'UPnP Device Host' service to determine if the UPnP service is running
    Affected if The UPnP service is enabled and running (required for exploitation)
  4. Confirm file version of upnp.dll
    Right-click upnp.dll in %SystemRoot%\System32\, select Properties, then Details to view file version; or use 'powershell (Get-Item C:\Windows\System32\upnp.dll).VersionInfo'
    Affected if File version is present and the service is active on a vulnerable Windows build

If the system runs a Windows version with a build number below the thresholds listed AND the UPnP service (upnphost) is enabled, the environment is potentially affected by this information disclosure vulnerability.

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.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Interim mitigation

Apply the relevant Microsoft security patch for this vulnerability when released. If UPnP is not required, consider disabling the service to reduce attack surface.

Recommended fix High confidence

Windows 10: Upgrade to respective builds (10.0.14393.9339, 10.0.17763.9020, 10.0.19044.7548, or 10.0.19045.7548) depending on version. Windows 11: Upgrade to builds 10.0.26100.8875, 10.0.26200.8875, or 10.0.28000.2525. Windows Server 2012/R2: Migrate to Windows Server 2016/2019/2022.

  1. 1. Identify the current Windows build version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt
  2. 2. Determine which Windows version (1607, 1809, 21h2, 22h2, 24h2, 25h2, 26h1, or Server 2012/R2) is installed
  3. 3. For Windows 10 (1607): Upgrade to build 10.0.14393.9339 or later via Windows Update or ISO media
  4. 4. For Windows 10 (1809): Upgrade to build 10.0.17763.9020 or later via Windows Update or ISO media
  5. 5. For Windows 10 (21h2): Upgrade to build 10.0.19044.7548 or later via Windows Update or ISO media
  6. 6. For Windows 10 (22h2): Upgrade to build 10.0.19045.7548 or later via Windows Update or ISO media
  7. 7. For Windows 11 (24h2): Upgrade to build 10.0.26100.8875 or later via Windows Update or ISO media
  8. 8. For Windows 11 (25h2): Upgrade to build 10.0.26200.8875 or later via Windows Update or ISO media
Caveat Windows Server 2012/R2 has no patch; requires migration to newer server OS which may require application compatibility testing. Consumer Windows 10 versions 1607 and 1809 are also out of mainstream support.

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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