Cyber Resilience

CVE-2026-49180

Microsoft Windows 10 21H2 ≤ 10.0.19044.7548

Published
14 July 2026
Modified
22 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0032 25th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-49180 is a medium-severity Link Following (CWE-59) vulnerability in Microsoft Windows 10 21H2. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 25th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

Improper link resolution before file access ('link following') in Universal Plug and Play (upnp.dll) allows an authorized attacker to disclose information locally.

CWE(s)
CWE-59

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
Why these techniques?

Link following in upnp.dll directly enables unauthorized local file reads, facilitating data collection from the local system.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-32212Same product: Microsoft Windows 10 1607
CVE-2026-49791Same product: Microsoft Windows 10 1607
CVE-2026-42989Same product: Microsoft Windows 10 1607
CVE-2026-45586Same product: Microsoft Windows 10 1607
CVE-2026-25187Same product: Microsoft Windows 10 1607
CVE-2025-59510Same product: Microsoft Windows 10 1607
CVE-2026-50469Same product: Microsoft Windows 10 1809
CVE-2026-49176Same product: Microsoft Windows 10 1607
CVE-2025-21274Same product: Microsoft Windows 10 1607
CVE-2025-21347Same product: Microsoft Windows 10 1607

Affected Assets

microsoft
windows 10 1607
≤ 10.0.14393.9339 · ≤ 10.0.14393.9339
microsoft
windows 10 1809
≤ 10.0.17763.9020 · ≤ 10.0.17763.9020
microsoft
windows 10 21h2
≤ 10.0.19044.7548 · ≤ 10.0.19044.7548 · ≤ 10.0.19044.7548
microsoft
windows 10 22h2
≤ 10.0.19045.7548 · ≤ 10.0.19045.7548 · ≤ 10.0.19045.7548
microsoft
windows 11 24h2
≤ 10.0.26100.8875 · ≤ 10.0.26100.8875
microsoft
windows 11 25h2
≤ 10.0.26200.8875 · ≤ 10.0.26200.8875
microsoft
windows 11 26h1
≤ 10.0.28000.2269 · ≤ 10.0.28000.2525
microsoft
windows server 2012
all versions, r2
microsoft
windows server 2016
≤ 10.0.14393.9339
microsoft
windows server 2019
≤ 10.0.17763.9020
+2 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.4.2

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require code to validate paths and avoid unsafe link following.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect link-following flaws before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.

A.8.26 Application security requirements partial match
prevents

Application security requirements can explicitly require safe handling of symbolic links and path traversal.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include input validation and safe file-access design patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address canonicalization and symlink attacks during implementation.

A.8.3 Information access restriction none match
none

Access-control rules can limit which files are reachable, reducing exposure to malicious links.

References