Skip to content
Server Security Center
KEVhigh7.8 Used in ransomware campaigns

CVE-2019-1069: Microsoft Task Scheduler Privilege Escalation

Microsoft Task Scheduler · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-15.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
6.2%
higher than 93.6% of all CVEs
Added to CISA KEV
2022-03-15
US federal due date 2022-04-05
Automatable (CISA SSVC)
no
technical impact: total

CVE-2019-1069 explained

CVE-2019-1069 is an elevation of privilege vulnerability in the Microsoft Task Scheduler Service on Windows. The service does not correctly validate certain file operations, a link-following weakness (CWE-59). It matters because CISA lists it as known exploited, including known ransomware use, and successful exploitation can give an attacker elevated privileges.

Impact

An attacker who already has unprivileged code execution on a victim system can gain elevated privileges. No user interaction is needed. Confidentiality, integrity and availability impacts are all high. CISA's SSVC rates the technical impact as total, meaning total control of the affected component, and rates it as not automatable. CISA reports the vulnerability is exploited in the wild and used in ransomware campaigns.

Who is affected

The CVE record lists builds before the security update of 2019-06-11 for Windows 10 Version 1703, 1709, 1803, 1809 and 1903 (32-bit, x64 and ARM64 where listed), Windows Server 2019 (including Server Core), and Windows Server, version 1803 and version 1903 (Server Core installation). The fix is in the security update of 2019-06-11. Further products are listed on this page.

Written with AI from the data on this page and checked against it automatically.

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.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 170332-bit, x64
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows 10 Version 180332-bit, x64, ARM64
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows Server, version 1803 (Server Core Installation)x64
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows Server 2019x64
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows 10 Version 1709 for 32-bit Systems32-bit
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows 10 Version 1709x64, ARM64
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows 10 Version 1903 for 32-bit Systems
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows 10 Version 1903 for x64-based Systems
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
Show 6 more products
  • Microsoft Windows 10 Version 1903 for ARM64-based Systems
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows Server, version 1903 (Server Core installation)x64
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows Server 2016x64
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • builds before the security update of 2019-06-11
    Fixed in
    • security update of 2019-06-11

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1703: security update of 2019-06-11
    • Microsoft Windows 10 Version 1803: security update of 2019-06-11
    • Microsoft Windows Server, version 1803 (Server Core Installation): security update of 2019-06-11
    • Microsoft Windows 10 Version 1809: security update of 2019-06-11
    • Microsoft Windows Server 2019: security update of 2019-06-11
    • Microsoft Windows Server 2019 (Server Core installation): security update of 2019-06-11
    Fixed versions for 10 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2019-1069
  • CISA's deadline for US federal agencies: 2022-04-05 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update of 2019-06-11, or a later cumulative update, on all affected Windows 10 and Windows Server systems.
  2. Follow the Microsoft vendor advisory for the exact update for each Windows version and platform.
  3. Prioritize patching, since CISA lists this as known exploited and used by ransomware.
  4. Limit who can run code on systems, as exploitation requires existing unprivileged code execution.
  5. Check unpatched systems for signs of compromise, such as unexpected privilege changes.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

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

Questions about CVE-2019-1069

Can this be exploited remotely without access?
No. The attacker needs unprivileged code execution on the victim system first. The vulnerability then lets them gain elevated privileges.
Is CVE-2019-1069 exploited in the wild?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-15 and notes known ransomware use. The US federal due date was 2022-04-05.
Which update fixes it?
The CVE record names the security update of 2019-06-11 as the fix for all listed Windows versions. CISA's required action is to apply updates per vendor instructions.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.