# CVE-2019-1253: Microsoft Windows AppX Deployment Server Privilege Escalation

> An attacker with local execution can exploit improper junction handling in the Windows AppX Deployment Server to elevate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 15 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-wp5j-ppw9-22mw

## What is CVE-2019-1253?

CVE-2019-1253 is a high-severity vulnerability in Microsoft Windows 10 1809, published on 11 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2019-1253?

It affects 8 products.


Products: Microsoft Windows 10 1703, Microsoft Windows 10 1709, Microsoft Windows 10 1803, Microsoft Windows 10 1809, Microsoft Windows 10 1903, Microsoft Windows Server 1803, Microsoft Windows Server 1903, Microsoft Windows Server 2019.

## How do I fix CVE-2019-1253?

No fix has been published for CVE-2019-1253 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 5 Apr 2022.

## Is CVE-2019-1253 being exploited?

Yes. Attackers have exploited CVE-2019-1253 in the wild since at least 15 Mar 2022, including in ransomware campaigns.

Public exploit code:

- Poc for CVE-2019-1253 (github_poc): https://github.com/padovah4ck/CVE-2019-1253
- https://github.com/rogue-kdc/CVE-2019-1253 (github_poc): https://github.com/rogue-kdc/CVE-2019-1253
- AppXSvc Arbitrary File Security Descriptor Overwrite EoP (github_poc): https://github.com/sgabe/CVE-2019-1253
- https://github.com/likekabin/CVE-2019-1253 (github_poc): https://github.com/likekabin/CVE-2019-1253
- AppXSvc - Privilege Escalation (exploitdb)

## Other vulnerabilities in Microsoft Windows 10 1809

- [CVE-2018-8414](https://insights.sbomify.com/CVE-2018-8414/): Microsoft Windows Shell Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2019-1129](https://insights.sbomify.com/CVE-2019-1129/): Microsoft Windows AppX Deployment Service (AppXSVC) Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2019-0841](https://insights.sbomify.com/CVE-2019-0841/): Microsoft Windows AppX Deployment Service (AppXSVC) Privilege Escalation (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1253 and fix it if it is affected.

What it is: CVE-2019-1253 is a high-severity vulnerability in Microsoft Windows 10 1809, published on 11 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-1253 in the wild since at least 15 Mar 2022, including in ransomware campaigns.

Affected product: Microsoft Windows 10 1809. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-1253/ (Markdown: https://insights.sbomify.com/CVE-2019-1253/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1253
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1253
- OSV: https://osv.dev/vulnerability/CVE-2019-1253

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-1253/
Summaries are generated and may contain mistakes; the official description above is the record.