CVE-2019-0841

HIGHNVD 7.89.0
EchelonGraph scoreHIGH confidence

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.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
7.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 41%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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-0730, CVE-2019-0731, CVE-2019-0796, CVE-2019-0805, CVE-2019-0836.

CVSS v3
7.8
EG Score
9.0(high)
EPSS
98.5%
KEV
⚠ Exploited

Published

April 9, 2019

Last Modified

October 29, 2025

Advisory Details (8)

Auto-updated Jun 3, 2026
🔬 Proof of concept available. Patch available. Sources: microsoft.

Weakness 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 139× in last 7d / 596× 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 844 total refreshes for this CVE.

  1. 2026-07-12 06:26 UTCEG score recompute
  2. 2026-07-12 06:26 UTCVendor advisory
  3. 2026-07-12 06:26 UTCGHSA enrichment
  4. 2026-07-12 05:43 UTCEPSS rescore
  5. 2026-07-12 02:41 UTCEG score recompute
  6. 2026-07-12 02:41 UTCVendor advisory
  7. 2026-07-12 02:41 UTCGHSA enrichment
  8. 2026-07-11 22:56 UTCEG score recompute
  9. 2026-07-11 22:56 UTCVendor advisory
  10. 2026-07-11 22:56 UTCGHSA enrichment
  11. 2026-07-11 19:11 UTCEG score recompute
  12. 2026-07-11 19:11 UTCVendor advisory
  13. 2026-07-11 19:11 UTCGHSA enrichment
  14. 2026-07-11 15:26 UTCEG score recompute
  15. 2026-07-11 15:26 UTCVendor advisory
  16. 2026-07-11 15:26 UTCGHSA enrichment
  17. 2026-07-11 11:41 UTCEG score recompute
  18. 2026-07-11 11:41 UTCVendor advisory
  19. 2026-07-11 11:41 UTCGHSA enrichment
  20. 2026-07-11 07:56 UTCEG score recompute
  21. 2026-07-11 07:56 UTCVendor advisory
  22. 2026-07-11 07:56 UTCGHSA enrichment
  23. 2026-07-11 04:11 UTCEG score recompute
  24. 2026-07-11 04:11 UTCVendor advisory
  25. 2026-07-11 04:11 UTCGHSA enrichment
Show 75 more
  1. 2026-07-11 00:25 UTCEG score recompute
  2. 2026-07-11 00:25 UTCVendor advisory
  3. 2026-07-11 00:25 UTCGHSA enrichment
  4. 2026-07-10 20:40 UTCEG score recompute
  5. 2026-07-10 20:40 UTCVendor advisory
  6. 2026-07-10 20:40 UTCGHSA enrichment
  7. 2026-07-10 17:52 UTCCISA KEV update
  8. 2026-07-10 16:55 UTCEG score recompute
  9. 2026-07-10 16:55 UTCVendor advisory
  10. 2026-07-10 16:55 UTCGHSA enrichment
  11. 2026-07-10 13:09 UTCEG score recompute
  12. 2026-07-10 13:09 UTCVendor advisory
  13. 2026-07-10 13:09 UTCGHSA enrichment
  14. 2026-07-10 09:24 UTCEG score recompute
  15. 2026-07-10 09:24 UTCVendor advisory
  16. 2026-07-10 09:24 UTCGHSA enrichment
  17. 2026-07-10 05:37 UTCEG score recompute
  18. 2026-07-10 05:37 UTCVendor advisory
  19. 2026-07-10 05:37 UTCGHSA enrichment
  20. 2026-07-10 01:51 UTCEG score recompute
  21. 2026-07-10 01:51 UTCVendor advisory
  22. 2026-07-10 01:51 UTCGHSA enrichment
  23. 2026-07-09 22:06 UTCEG score recompute
  24. 2026-07-09 22:06 UTCVendor advisory
  25. 2026-07-09 22:06 UTCGHSA enrichment
  26. 2026-07-09 19:06 UTCEPSS rescore
  27. 2026-07-09 18:21 UTCEG score recompute
  28. 2026-07-09 18:21 UTCVendor advisory
  29. 2026-07-09 18:21 UTCGHSA enrichment
  30. 2026-07-09 14:36 UTCEG score recompute
  31. 2026-07-09 14:36 UTCVendor advisory
  32. 2026-07-09 14:36 UTCGHSA enrichment
  33. 2026-07-09 10:50 UTCEG score recompute
  34. 2026-07-09 10:50 UTCVendor advisory
  35. 2026-07-09 10:50 UTCGHSA enrichment
  36. 2026-07-09 07:03 UTCEG score recompute
  37. 2026-07-09 07:03 UTCVendor advisory
  38. 2026-07-09 07:03 UTCGHSA enrichment
  39. 2026-07-09 03:18 UTCEG score recompute
  40. 2026-07-09 03:18 UTCVendor advisory
  41. 2026-07-09 03:18 UTCGHSA enrichment
  42. 2026-07-08 23:33 UTCEG score recompute
  43. 2026-07-08 23:33 UTCVendor advisory
  44. 2026-07-08 23:33 UTCGHSA enrichment
  45. 2026-07-08 19:48 UTCEG score recompute
  46. 2026-07-08 19:48 UTCVendor advisory
  47. 2026-07-08 19:48 UTCGHSA enrichment
  48. 2026-07-08 16:00 UTCEG score recompute
  49. 2026-07-08 16:00 UTCVendor advisory
  50. 2026-07-08 16:00 UTCGHSA enrichment
  51. 2026-07-08 12:15 UTCEG score recompute
  52. 2026-07-08 12:15 UTCVendor advisory
  53. 2026-07-08 12:15 UTCGHSA enrichment
  54. 2026-07-08 08:29 UTCEG score recompute
  55. 2026-07-08 08:29 UTCVendor advisory
  56. 2026-07-08 08:29 UTCGHSA enrichment
  57. 2026-07-08 04:44 UTCEG score recompute
  58. 2026-07-08 04:44 UTCVendor advisory
  59. 2026-07-08 04:44 UTCGHSA enrichment
  60. 2026-07-08 00:56 UTCEG score recompute
  61. 2026-07-08 00:56 UTCVendor advisory
  62. 2026-07-08 00:56 UTCGHSA enrichment
  63. 2026-07-07 21:12 UTCEG score recompute
  64. 2026-07-07 21:12 UTCVendor advisory
  65. 2026-07-07 21:12 UTCGHSA enrichment
  66. 2026-07-07 19:01 UTCCISA KEV update
  67. 2026-07-07 17:26 UTCEG score recompute
  68. 2026-07-07 17:26 UTCVendor advisory
  69. 2026-07-07 17:26 UTCGHSA enrichment
  70. 2026-07-07 17:16 UTCCISA KEV update
  71. 2026-07-07 13:42 UTCEPSS rescore
  72. 2026-07-07 13:42 UTCEPSS rescore
  73. 2026-07-07 13:38 UTCEG score recompute
  74. 2026-07-07 13:38 UTCVendor advisory
  75. 2026-07-07 13:38 UTCGHSA enrichment

Publicly available exploits

(8 references)

Working exploit code is in the public domain (1 Metasploit module) (3 GitHub PoCs) (4 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-47128✓ verified
    First seen Jul 16, 2019

    Microsoft Windows 10 < build 17763 - AppXSvc Hard Link Privilege Escalation (Metasploit)

    Open source ↗
  • GitHub PoC0x00-0x00/CVE-2019-0841-BYPASS
    First seen Jun 11, 2019

    A fully automatic CVE-2019-0841 bypass targeting all versions of Edge in Windows 10.

    Open source ↗
  • Exploit-DBEDB-46976
    First seen Jun 7, 2019

    Microsoft Windows - AppX Deployment Service Local Privilege Escalation (3)

    Open source ↗
  • Exploit-DBEDB-46938
    First seen May 23, 2019

    Microsoft Windows - AppX Deployment Service Local Privilege Escalation (2)

    Open source ↗
  • GitHub PoClikekabin/CVE-2019-0841
    First seen Apr 10, 2019
    Open source ↗
  • Exploit-DBEDB-46683
    First seen Apr 9, 2019

    Microsoft Windows - AppX Deployment Service Privilege Escalation

    Open source ↗
  • Metasploitexploit/windows/local/appxsvc_hard_link_privesc✓ verified
    First seen Apr 9, 2019

    AppXSvc Hard Link Privilege Escalation

    Open source ↗
  • GitHub PoCrogue-kdc/CVE-2019-0841
    First seen Apr 5, 2019

    PoC code for CVE-2019-0841 Privilege Escalation vulnerability

    Open source ↗

Frequently asked(6)

What is CVE-2019-0841?
CVE-2019-0841 is a high vulnerability published on April 9, 2019. 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-0730, CVE-2019-0731, CVE-2019-0796, CVE-2019-0805, CVE-2019-0836.
When was CVE-2019-0841 disclosed?
CVE-2019-0841 was first published in the National Vulnerability Database on April 9, 2019, with the most recent update on October 29, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-0841 actively exploited?
Yes. CISA added CVE-2019-0841 to the Known Exploited Vulnerabilities catalog on March 15, 2022, affecting Microsoft Windows. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2019-0841?
CVE-2019-0841 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2019-0841?
CVE-2019-0841 affects Microsoft Windows. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2019-0841?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-0841, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-0841

Explore →

Is Your Infrastructure Affected by CVE-2019-0841?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.