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.
CVE-2019-1064
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-15), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 9.0(high)
- EPSS
- 93.3%
- KEV
- ⚠ Exploited
Published
June 12, 2019
Last Modified
October 29, 2025
Advisory Details (3)
Auto-updated Jun 3, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-1064Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1064Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-1064Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 141× in last 7d / 599× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 757 total refreshes for this CVE.
- 2026-07-07 12:04 UTCEG score recompute
- 2026-07-07 12:04 UTCVendor advisory
- 2026-07-07 12:04 UTCGHSA enrichment
- 2026-07-07 08:16 UTCEG score recompute
- 2026-07-07 08:16 UTCVendor advisory
- 2026-07-07 08:16 UTCGHSA enrichment
- 2026-07-07 04:29 UTCEG score recompute
- 2026-07-07 04:29 UTCVendor advisory
- 2026-07-07 04:29 UTCGHSA enrichment
- 2026-07-07 00:42 UTCEG score recompute
- 2026-07-07 00:42 UTCVendor advisory
- 2026-07-07 00:42 UTCGHSA enrichment
- 2026-07-06 20:55 UTCEG score recompute
- 2026-07-06 20:55 UTCVendor advisory
- 2026-07-06 20:55 UTCGHSA enrichment
- 2026-07-06 17:07 UTCEG score recompute
- 2026-07-06 17:07 UTCVendor advisory
- 2026-07-06 17:07 UTCGHSA enrichment
- 2026-07-06 16:25 UTCEPSS rescore
- 2026-07-06 16:25 UTCEPSS rescore
- 2026-07-06 13:18 UTCEG score recompute
- 2026-07-06 13:18 UTCVendor advisory
- 2026-07-06 13:18 UTCGHSA enrichment
- 2026-07-06 09:28 UTCEG score recompute
- 2026-07-06 09:28 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-06 09:28 UTCGHSA enrichment
- 2026-07-06 05:40 UTCEG score recompute
- 2026-07-06 05:40 UTCVendor advisory
- 2026-07-06 05:39 UTCGHSA enrichment
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-06 01:52 UTCEG score recompute
- 2026-07-06 01:52 UTCVendor advisory
- 2026-07-06 01:52 UTCGHSA enrichment
- 2026-07-05 22:05 UTCEG score recompute
- 2026-07-05 22:05 UTCVendor advisory
- 2026-07-05 22:05 UTCGHSA enrichment
- 2026-07-05 18:18 UTCEG score recompute
- 2026-07-05 18:18 UTCVendor advisory
- 2026-07-05 18:17 UTCGHSA enrichment
- 2026-07-05 14:28 UTCEG score recompute
- 2026-07-05 14:28 UTCVendor advisory
- 2026-07-05 14:28 UTCGHSA enrichment
- 2026-07-05 10:40 UTCEG score recompute
- 2026-07-05 10:40 UTCVendor advisory
- 2026-07-05 10:40 UTCGHSA enrichment
- 2026-07-05 06:53 UTCEG score recompute
- 2026-07-05 06:53 UTCVendor advisory
- 2026-07-05 06:53 UTCGHSA enrichment
- 2026-07-05 03:06 UTCEG score recompute
- 2026-07-05 03:06 UTCVendor advisory
- 2026-07-05 03:06 UTCGHSA enrichment
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-04 23:19 UTCEG score recompute
- 2026-07-04 23:19 UTCVendor advisory
- 2026-07-04 23:18 UTCGHSA enrichment
- 2026-07-04 19:30 UTCEG score recompute
- 2026-07-04 19:30 UTCVendor advisory
- 2026-07-04 19:30 UTCGHSA enrichment
- 2026-07-04 15:42 UTCEG score recompute
- 2026-07-04 15:42 UTCVendor advisory
- 2026-07-04 15:42 UTCGHSA enrichment
- 2026-07-04 11:53 UTCEG score recompute
- 2026-07-04 11:53 UTCVendor advisory
- 2026-07-04 11:53 UTCGHSA enrichment
- 2026-07-04 08:06 UTCEG score recompute
- 2026-07-04 08:06 UTCVendor advisory
- 2026-07-04 08:06 UTCGHSA enrichment
- 2026-07-04 06:28 UTCEPSS rescore
- 2026-07-04 04:18 UTCEG score recompute
- 2026-07-04 04:18 UTCVendor advisory
- 2026-07-04 04:18 UTCGHSA enrichment
- 2026-07-04 00:30 UTCEG score recompute
- 2026-07-04 00:30 UTCVendor advisory
- 2026-07-04 00:30 UTCGHSA enrichment
- 2026-07-03 20:42 UTCEG score recompute
- 2026-07-03 20:42 UTCVendor advisory
- 2026-07-03 20:42 UTCGHSA enrichment
- 2026-07-03 16:54 UTCEG score recompute
- 2026-07-03 16:54 UTCVendor advisory
- 2026-07-03 16:54 UTCGHSA enrichment
- 2026-07-03 13:07 UTCEG score recompute
- 2026-07-03 13:07 UTCVendor advisory
- 2026-07-03 13:07 UTCGHSA enrichment
- 2026-07-03 09:20 UTCEG score recompute
- 2026-07-03 09:20 UTCVendor advisory
- 2026-07-03 09:20 UTCGHSA enrichment
- 2026-07-03 05:33 UTCEG score recompute
- 2026-07-03 05:33 UTCVendor advisory
- 2026-07-03 05:33 UTCGHSA enrichment
- 2026-07-03 01:45 UTCEG score recompute
- 2026-07-03 01:45 UTCVendor advisory
- 2026-07-03 01:45 UTCGHSA enrichment
- 2026-07-02 21:57 UTCEG score recompute
- 2026-07-02 21:57 UTCVendor advisory
- 2026-07-02 21:57 UTCGHSA enrichment
- 2026-07-02 18:10 UTCEG score recompute
- 2026-07-02 18:10 UTCVendor advisory
- 2026-07-02 18:10 UTCGHSA enrichment
- 2026-07-02 14:22 UTCEG score recompute
- 2026-07-02 14:22 UTCVendor advisory
Publicly available exploits
(2 references)Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCRythmStick/CVE-2019-1064First seen Jun 12, 2019
CVE-2019-1064 Local Privilege Escalation Vulnerability
Open source ↗ - GitHub PoC0x00-0x00/CVE-2019-1064First seen Jun 12, 2019
CVE-2019-1064 Local Privilege Escalation Vulnerability
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 93%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Frequently asked(6)
What is CVE-2019-1064?
When was CVE-2019-1064 disclosed?
Is CVE-2019-1064 actively exploited?
What is the CVSS score of CVE-2019-1064?
Which products are affected by CVE-2019-1064?
How do I remediate CVE-2019-1064?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2019-1064
Is Your Infrastructure Affected by CVE-2019-1064?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.