Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2019-1069: Windows Task Scheduler Local Privilege Escalation

Published Jun 12, 2019 · Updated 9 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS6.2%94th percentile
CISA KEVYesAdded Mar 15, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2019-1069CWE-20

CVE-2019-1069 is a local privilege escalation vulnerability in Microsoft Windows Task Scheduler Service. Improper validation of file operations involving SetJobFileSecurityByName() allows an attacker executing code with limited privileges to escalate to SYSTEM. Affected products include Windows 10 versions 1703, 1803, 1809, and 1903, and Windows Server 2016 and 2019 across multiple architectures.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can elevate a limited user to SYSTEM and grant access to protected files, potentially resulting in complete compromise of the affected host. The vulnerability supports post-compromise privilege escalation rather than unauthenticated remote code execution. Exploitation has been associated with Conti affiliates and TargetCompany ransomware activity.

Mitigation

If you can’t patch tonight, do this now.

Until patched, restrict untrusted code execution and access to schtasks.exe. Monitor suspicious Task Scheduler activity, particularly use of legacy Task Scheduler components. These compensating controls do not replace the security update.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update addressing CVE-2019-1069 for the installed Windows release, or upgrade to a Windows version containing the fix. The update corrects Task Scheduler file-operation validation. Deploy through Windows Update, WSUS, or SCCM, and verify successful installation.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10operating_system
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1703operating_system
Microsoft CorporationWindows 10 1709operating_system
Microsoft CorporationWindows 10 1803operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 1903operating_system
Microsoft CorporationWindows Server 1803operating_system
Microsoft CorporationWindows Server 1903operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
FAQ

Frequently asked questions

Is CVE-2019-1069 exploited in the wild?
Yes. As of Nov 9, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 15, 2022.
Is there a public exploit for CVE-2019-1069?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2019-1069, the earliest disclosed Jun 3, 2019.
Is there a patch for CVE-2019-1069?
Apply the Microsoft security update addressing CVE-2019-1069 for the installed Windows release, or upgrade to a Windows version containing the fix. The update corrects Task Scheduler file-operation validation.
What products are affected by CVE-2019-1069?
Microsoft Corporation Windows 10, Microsoft Corporation Windows Server 2016, Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1703, and 7 more.
How severe is CVE-2019-1069?
CVE-2019-1069 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 6.2% (94th percentile) as of Nov 9, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence2Every report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.