Evidence used
- CISA confirms exploitation in the wild.
- A structured source references public exploit or proof-of-concept material.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 6.12% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2019
CVE-2019-1069High confidence
Microsoft Task Scheduler Privilege Escalation Vulnerability
Microsoft · Task Scheduler
7.8HighCVSS 3.1
Patch now
Patch availableCISA confirms exploitation in the wild and lists 2022-04-05 as the remediation due date.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 15 Mar 2022
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs Microsoft Task Scheduler and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
CISA confirms exploitation in the wild and lists 2022-04-05 as the remediation due date.
Patch available01
What, why and how
A privilege escalation vulnerability exists in the way the Task Scheduler Service validates certain file operations.
What
A privilege escalation vulnerability exists in the way the Task Scheduler Service validates certain file operations.
Why
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.
What
A privilege escalation vulnerability exists in the way the Task Scheduler Service validates certain file operations.
Why
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation Confirmed in the wild
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2022-03-15. Known ransomware campaign use is recorded.
Public PoC / exploit material Reference recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
- Likely attack path
- local access → Improper Link Resolution Before File Access ('Link Following') → gain additional privileges
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-59 ↗
CWE-59: Improper Link Resolution Before File Access ('Link Following'). The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Windows 10 Version 1803: 10.0.0 < publication
- Windows 10 Version 1709 for 32-bit Systems: 10.0.0 < publication
- Windows Server 2019: 10.0.17763.0 < publication
- Windows Server 2016: 10.0.14393.0 < publication
- Windows 10 Version 1903 for 32-bit Systems: 10.0.0 < publication
- Windows Server, version 1803 (Server Core Installation): 10.0.0 < publication
- Windows 10 Version 1903 for x64-based Systems: 10.0.0 < publication
- Windows 10 Version 1507: 10.0.10240.0 < publication
- Windows 10 Version 1809: 10.0.0 < publication, 10.0.17763.0 < publication
- Windows 10 Version 1703: 10.0.0 < publication
- Windows 10 Version 1607: 10.0.14393.0 < publication
- Windows Server 2019 (Server Core installation): 10.0.17763.0 < publication
- Windows 10 Version 1903 for ARM64-based Systems: 10.0.0 < publication
- Windows 10 Version 1709: 10.0.0 < publication
- Windows Server, version 1903 (Server Core installation): 10.0.0 < publication
- Windows Server 2016 (Server Core installation): 10.0.14393.0 < publication
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 12 Jun 2019 · Last source change 12 Aug 2026, 03:55 UTC · CWE-59 · Improper Link Resolution Before File Access ('Link Following')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-01
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2019-9651
Product sourceCISA KEV
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA known-exploited stateENISA EUVD now records this CVE in its known-exploited dataset.ENISA EUVD ↗
- Before
- not listed in ENISA EUVD known-exploited dataset
- After
- listed in ENISA EUVD known-exploited dataset (EUVD-2019-9651)
- ENISA EUVD mappingEUVD-2019-9651 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2019-9651"}
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 10.0.0 < publication; 10.0.17763.0 < publication · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- Windows 10 Version 1703: 10.0.0 < publication; Windows 10 Version 1803: 10.0.0 < publication; Windows Server, version 1803 (Server Core Installation): 10.0.0 < publication; Windows 10 Version 1809: 10.0.17763.0 < publication, 10.0.0 < publication; Windows Server 2019: 10.0.17763.0 < publication; Windows Server 2019 (Server Core installation): 10.0.17763.0 < publication; Windows 10 Version 1709 for 32-bit Systems: 10.0.0 < publication; Windows 10 Version 1709: 10.0.0 < publication; Windows 10 Version 1903 for 32-bit Systems: 10.0.0 < publication; Windows 10 Version 1903 for x64-based Systems: 10.0.0 < publication; Windows 10 Version 1903 for ARM64-based Systems: 10.0.0 < publication; Windows Server, version 1903 (Server Core installation): 10.0.0 < publication; Windows 10 Version 1507: 10.0.10240.0 < publication; Windows 10 Version 1607: 10.0.14393.0 < publication; Windows Server 2016: 10.0.14393.0 < publication; Windows Server 2016 (Server Core installation): 10.0.14393.0 < publication · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Vendor guidanceAuthoritative vendor guidance changed: added patch: msrc.microsoft.com/CVE-2019-1069; added patch: portal.msrc.microsoft.com/CVE-2019-1069; removed vendor advisory: msrc.microsoft.com/CVE-2019-1069; 1 further additions.secure@microsoft.com ↗
- Before
- vendor advisory: msrc.microsoft.com/CVE-2019-1069
- After
- patch: msrc.microsoft.com/CVE-2019-1069 · patch: portal.msrc.microsoft.com/CVE-2019-1069 · remediation: msrc.microsoft.com/CVE-2019-1069
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 10.0.0 < publication; 10.0.17763.0 < publication · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 10.0.0 < publication; 10.0.17763.0 < publication · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.secure@microsoft.com ↗
- Before
- Awaiting fix
- After
- Patch available
- Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.blog.0patch.com ↗
- Before
- No public exploit
- After
- Public exploit reference
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Added to CISA KEV
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.