CVE-2019-1130
Microsoft Windows 10 1709
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2019-1130 is a high-severity Link Following (CWE-59) vulnerability in Microsoft Windows 10 1709. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked in the top 18% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
An elevation of privilege vulnerability exists in the Windows AppX Deployment Service (AppXSVC) due to improper handling of hard links. The flaw, tracked as CVE-2019-1130 and distinct from CVE-2019-1129, carries a CVSS 3.1 base score of 7.8 and is associated with CWE-59. It affects the AppX deployment component on supported Windows platforms.
A local attacker with low privileges can exploit the issue without user interaction to obtain full elevation of privilege, resulting in high impact to confidentiality, integrity, and availability on the affected system. The attack vector is local and requires only standard user rights to trigger the hard-link mishandling within AppXSVC.
Microsoft has published security guidance for CVE-2019-1130 through its Security Response Center, and the vulnerability appears in CISA's catalog of known exploited vulnerabilities, confirming observed in-the-wild use.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2019-9707
Vulnerability Data
An elevation of privilege vulnerability exists when Windows AppX Deployment Service (AppXSVC) improperly handles hard links, aka 'Windows Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2019-1129.
- CWE(s)
- KEV Date Added
- 23 May 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
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.
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.
Security testing can detect link-following flaws before release.
Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.
Application security requirements can explicitly require safe handling of symbolic links and path traversal.
Secure architecture principles include input validation and safe file-access design patterns.
Secure coding standards directly address canonicalization and symlink attacks during implementation.
Access-control rules can limit which files are reachable, reducing exposure to malicious links.