CVE-2019-1253

CRITICALNVD 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 — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 12%CVSS: 7.8Exploit: cisa kev · ssvc active · kev ransomware · epss top5pct · public exploitExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

An elevation of privilege vulnerability exists when the Windows AppX Deployment Server improperly handles junctions.To exploit this vulnerability, an attacker would first have to gain execution on the victim system, aka 'Windows Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2019-1215, CVE-2019-1278, CVE-2019-1303.

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
12%
EPSS %ILE
95th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 11, 2019

Last Modified

October 29, 2025

Advisory Details (2)

Auto-updated Jun 3, 2026
⚠️ Active exploitation confirmed. Fix referenced — no release confirmed yet. Sources: microsoft, cisa.
cisa🔴 Active Exploitation

Known 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-1253
microsoftMentions a patch (unverified)

Security 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-1253

Vendor Advisories for CVE-2019-1253(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 90× in last 7d / 400× 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 1,636 total refreshes for this CVE.

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

Publicly available exploits

(4 references)

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

  • Exploit-DBEDB-47389
    First seen Sep 16, 2019

    AppXSvc - Privilege Escalation

    Open source ↗
  • GitHub PoCpadovah4ck/CVE-2019-1253
    First seen Sep 11, 2019

    Poc for CVE-2019-1253

    Open source ↗
  • GitHub PoCsgabe/CVE-2019-1253
    First seen Sep 11, 2019

    AppXSvc Arbitrary File Security Descriptor Overwrite EoP

    Open source ↗
  • GitHub PoCrogue-kdc/CVE-2019-1253
    First seen Apr 10, 2019
    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2019-1253?
CVE-2019-1253 is a critical vulnerability published on September 11, 2019. An elevation of privilege vulnerability exists when the Windows AppX Deployment Server improperly handles junctions.To exploit this vulnerability, an attacker would first have to gain execution on the victim system, aka 'Windows Elevation of Privilege Vulnerability'. This CVE ID is unique from…
When was CVE-2019-1253 disclosed?
CVE-2019-1253 was first published on September 11, 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-1253 actively exploited?
Yes. CISA added CVE-2019-1253 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 attention. A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
What is the CVSS score of CVE-2019-1253?
CVE-2019-1253 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 (CRITICAL).
Which products are affected by CVE-2019-1253?
CVE-2019-1253 affects Microsoft Windows.
How do I remediate CVE-2019-1253?
A fix for CVE-2019-1253 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2019-1253 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2019-1253?

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

Book a Demo →Browse All CVEs