CVE Intelligence
CISA KEV High File handling

CVE-2019-1385 — Microsoft Windows AppX Deployment Extensions Privilege Escalation Vulnerability

An elevation of privilege vulnerability exists when the Windows AppX Deployment Extensions improperly performs privilege management, resulting in access to system files.To exploit this vulnerability, an authenticated attacker would need to run a specially crafted application to elevate privileges.The security update addresses the vulnerability by correcting how AppX Deployment Extensions manages privileges., aka 'Windows AppX Deployment Extensions Elevation of Privilege Vulnerability'.

Published Nov 12, 2019 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: microsoft

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · May 23, 2022 R used by ransomware (CISA)
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Used in ransomware campaigns (CISA)+10
  • EPSS 3.6% (30-day exploitation probability)+13
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed May 23, 2022
EPSS FIRST
3.6%
ahead of 89% of scored CVEs · Oct 14, 2026
Affects
Microsoft
Windows and 7 more
CVSS base
7.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Jun 13, 2022 — passed 1585 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Windows, Microsoft Windows 10 1709, Microsoft Windows 10 1803…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Microsoft Windows version 10 Version 1709 for 32-bit Systemsversion 10 Version 1709 for x64-based Systemsversion 10 Version 1803 for 32-bit Systemsversion 10 Version 1803 for x64-based Systemsversion 10 Version 1803 for ARM64-based Systemsversion 10 Version 1809 for 32-bit Systemsversion 10 Version 1809 for x64-based Systemsversion 10 Version 1809 for ARM64-based Systems
and 1 more version 10 Version 1709 for ARM64-based Systems
Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 1709 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 1803 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 1809 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 1903 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Server version 2019 (Core installation)version 2019version version 1803 (Core Installation) Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2016 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2019 versions not specified by the source Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.8 CVSS 3.1 High 1.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
7.8 CVSS 3.1 High 1.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.8 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
6.1 CVSS 2.0 Medium 3.9 8.5 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-59 · Link Following

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
May 23, 2022
Federal deadline
Jun 13, 2022
passed 1585 day(s) ago
Ransomware use
Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 3.60%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Monitor file creation in web directories and paths with traversal sequences (../).
  • Hunt retroactively in logs from before May 23, 2022 (KEV listing): exploitation may have started earlier.
endpoint telemetry (EDR)file integrity (FIM)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · microsoft/windows 10 1709, microsoft/windows 10 1803, microsoft/windows 10 1809, microsoft/windows 10 1903, microsoft/wi
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 13, 2026
  • Affected products added · microsoft/windows, microsoft/windows server
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • CVSS changed · 7.8
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2022
  • Added to CISA KEV catalog
    May 22, 2022 · CISA
  • 2019
  • CVE published
    Nov 12, 2019 · microsoft

Source activity

Repeated readings are counted rather than listed.

  • 3× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

6 on the record

Elsewhere on this site

Microsoft
every CVE for this vendor
2022-05
what else CISA listed that month
File handling
same class
CWE-59
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-97844 Role: DNS Server Information Disclosure Vulnerability 2d
  • CVE-2026-97843 Role: DNS Server Information Disclosure Vulnerability 2d
  • CVE-2026-97839 Role: DNS Server Information Disclosure Vulnerability 2d
  • CVE-2026-97840 Role: DNS Server Information Disclosure Vulnerability 2d
  • CVE-2026-97842 Role: DNS Server Information Disclosure Vulnerability 2d
  • CVE-2026-97841 Role: DNS Server Information Disclosure Vulnerability 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2019-1385 is "Microsoft Windows AppX Deployment Extensions Privilege Escalation Vulnerability", rated High. It affects Windows (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.8 describes technical severity. EPSS 3.60% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.