Threats / Microsoft / CVE-2019-1069
CVE-2019-1069
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Task Scheduler vulnerability
A privilege escalation vulnerability in Microsoft Task Scheduler allows attackers to execute code with elevated privileges by exploiting improper file operation validation.
Verdict
Today item, not a backlog item.
This vulnerability enables local privilege escalation through Task Scheduler's file handling. Exploitation has been observed in active ransomware campaigns, making it a significant risk for systems where local access is possible.
CISA KEV Yes · 2022-03-155Ransomware use Flagged5EPSS 0.06117 (verify live)6CVSS 7.83CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-15), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.06117 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 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) · Affected: Microsoft, Task Scheduler. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-59 Link Following — weakness family: Path traversal / file.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1007 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain local access to a target system through initial compromise or social engineering.
Business
An attacker establishes a foothold on the network, creating risk of lateral movement and data exfiltration.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the Task Scheduler file validation flaw to escalate my privileges to SYSTEM level.
Business
The attacker obtains administrative control, enabling deployment of ransomware or persistent backdoors across critical systems.
3
Lateral reach — past segmentation narrative 3
Attacker
I deploy ransomware or malware with system-level permissions to encrypt or exfiltrate sensitive data.
Business
Operations halt, data is compromised, and the organization faces ransom demands and regulatory penalties.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05