# CVE-2019-1069: Microsoft Task Scheduler Privilege Escalation

> An attacker with local code execution can exploit improper file operation validation in the Task Scheduler Service to gain elevated privileges on Windows systems.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **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:** 12 Jun 2019
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-gf8w-3v8h-w6hr

## What is CVE-2019-1069?

CVE-2019-1069 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 12 Jun 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 in the way the Task Scheduler Service validates certain file operations. An attacker who successfully exploited the vulnerability could gain elevated privileges on a victim system.
To exploit the vulnerability, an attacker would require unprivileged code execution on a victim system.
The security update addresses the vulnerability by correctly validating file operations.

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

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

It affects 11 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, 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 2016, Microsoft Windows Server 2019.

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

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

## Is CVE-2019-1069 being exploited?

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

Public exploit code:

- Privesc through import of Sheduled tasks + Hardlinks - CVE-2019-1069 (github_poc): https://github.com/S3cur3Th1sSh1t/SharpPolarBear

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1069 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 12 Jun 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-1069 in the wild since at least 15 Mar 2022, including in ransomware campaigns.

Affected product: Microsoft Windows 10 1507. 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-1069/ (Markdown: https://insights.sbomify.com/CVE-2019-1069/index.md)
```

## Sources

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

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