Actively exploitedKnown ransomware use

CVE-2019-1130 Microsoft Windows AppX Deployment Service Privilege Escalation Vulnerability

A privilege escalation vulnerability exists when Windows AppX Deployment Service (AppXSVC) improperly handles hard links.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch nowCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 23 May 2022.
  • CISA lists it as known to be used in ransomware campaigns.
  • Rated High severity (CVSS 7.8, scored by CISA).
  • It has been in the catalogue for 1,628 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

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.

Affected Versions

ProductVersions
Microsoft Windows Server2012
2012 (Core installation)
2012 R2
2012 R2 (Core installation)
2016
2016 (Core installation)
Microsoft Windows8.1 for x64-based systems
RT 8.1
10 for 32-bit Systems
10 for x64-based Systems
10 Version 1607 for 32-bit Systems
10 Version 1607 for x64-based Systems
Microsoft Windows 10 Version 1903 for 32-bit Systemsunspecified
Microsoft Windows 10 Version 1903 for x64-based Systemsunspecified
Microsoft Windows 10 Version 1903 for ARM64-based Systemsunspecified
Microsoft Windows Server, version 1903 (Server Core installation)unspecified

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Microsoft Windows. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply updates per vendor instructions.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2019-1130 and every other exploited flaw on the list.

Check My Exposure