CVE-2026-49180
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 · uneditedImproper link resolution before file access ('link following') in Universal Plug and Play (upnp.dll) allows an authorized attacker to disclose information locally.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
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 confidenceA link following vulnerability in the Universal Plug and Play (upnp.dll) component allows a local authorized attacker to resolve symbolic links improperly before file access, potentially reading sensitive files they shouldn't have access to.
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< 10.0.14393.9339< 10.0.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2269< 10.0.28000.2525all versions= r2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows build versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the Windows build numberAffected if The build number falls below any of these thresholds: 14393.9339 (1607), 17763.9020 (1809), 19044.7548 (21h2), 19045.7548 (22h2), 26100.8875 (24h2), 26200.8875 (25h2), 28000.2269 or 28000.2525 (26h1), or if running Windows Server 2012/R2
-
Locate upnp.dll versionFind the file at C:\Windows\System32\upnp.dll (or via 'dir /s C:\upnp.dll'), right-click Properties > Details to see File VersionAffected if The DLL exists and its version cannot be determined or is older than the patched builds corresponding to your Windows version
-
Verify UPnP service statusRun 'sc query upnphost' or check Services > UPnP Device Host in Task ManagerAffected if The UPnP Device Host service (upnphost) is running, as the vulnerable code path requires this service to be active
-
Check for symbolic link creation exposureReview file permissions on sensitive system or user files (check with 'icacls <filename>') to see if low-privilege authorized users have write access to directories containing files they should not accessAffected if Untrusted or low-privilege users have write access to directories that contain sensitive files, enabling potential symlink exploitation
You are affected if your Windows build version is below the patched thresholds AND the UPnP Device Host service is running, creating a condition where the upnp.dll symlink vulnerability could be exploited by a local authorized user.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.14393.933910.0.17763.902010.0.19044.7548
Apply vendor patches when available. Until then, restrict file system permissions on sensitive files and limit local access to trusted authorized users only.
Apply the Microsoft security update for CVE-2026-49180 to reach the fixed build versions specified (e.g., 10.0.14393.9339 or higher for Win10 1607)
- Identify the Windows version and build number of the affected system using 'winver' or 'systeminfo'
- Navigate to Windows Update Settings > Check for updates
- Install all available security updates for the system
- Alternatively, manually download and install the specific KB patch for this CVE from the Microsoft Update Catalog
- Verify the installation by checking that the build number matches or exceeds: 10.0.14393.9339 (Win10 1607), 10.0.17763.9020 (Win10 1809), 10.0.19044.7548 (Win10 21h2), 10.0.19045.7548 (Win10 22h2), 10.0.26100.8875 (Win11 24h2), 10.0.26200.8875 (Win11 25h2), or 10.0.28000.2525 (Win11 26h1)
- For Windows Server 2012/R2, apply the applicable security update from Microsoft's update catalog
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49180 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49180 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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