CVE-2019-1064

Windows Elevation of Privilege Vulnerability

HIGH
7.8
CVSS Score
Published: June 12, 2019 at 01:49 PM UTC
Updated: June 17, 2026 at 02:27 AM UTC
12 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows 10 1809

Using Windows 10 Version 1703 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1703 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploitation
CISA KEV
Exploit prediction
EPSS 7%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score6.9%

EPSS (Exploit Prediction Scoring System) estimates a 6.9% chance this CVE is exploited in the wild within the next 30 days — higher than 94% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

A privilege escalation vulnerability exists when Windows AppXSVC improperly handles hard links. An attacker who successfully exploited this vulnerability could run processes in an elevated context.

Required Action
Apply updates per vendor instructions.
Ransomware Use
Known
Added to KEV
Mar 15, 2022
Remediation Due
Apr 5, 2022
1666 days overdue

Description

An elevation of privilege vulnerability exists when Windows AppX Deployment Service (AppXSVC) improperly handles hard links. An attacker who successfully exploited this vulnerability could run processes in an elevated context. An attacker could then install programs; view, change or delete data. To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system. The security update addresses the vulnerability by correcting how Windows AppX Deployment Service handles hard links.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

10.0.0 ≤ v < publication
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.14393.0 ≤ v < publication10.0.14393.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.17763.0 ≤ v < publication10.0.010.0.17763.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-59

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card