CVE-2024-49039

Windows Task Scheduler Elevation of Privilege Vulnerability

HIGH
8.8
CVSS Score
Published: November 12, 2024 at 05:54 PM UTC
Updated: August 4, 2026 at 05:35 AM UTC
14 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows 10 1809

Using Windows Server 2025 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows Server 2025 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploitation
CISA KEV
Exploit prediction
EPSS 14%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score14.2%

EPSS (Exploit Prediction Scoring System) estimates a 14.2% chance this CVE is exploited in the wild within the next 30 days — higher than 97% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Microsoft Windows Task Scheduler contains a privilege escalation vulnerability that can allow an attacker-provided, local application to escalate privileges outside of its AppContainer, and access privileged RPC functions.

Required Action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Ransomware Use
Known
Added to KEV
Nov 12, 2024
Remediation Due
Dec 3, 2024
692 days overdue

Description

Windows Task Scheduler Elevation of Privilege Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.10240.2082610.0.10240.0 ≤ v < 10.0.10240.2082610.0.10240.0
Affected range stops below 10.0.10240.20826, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.751510.0.14393.0 ≤ v < 10.0.14393.751510.0.14393.0
Affected range stops below 10.0.14393.7515, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.653210.0.17763.0 ≤ v < 10.0.17763.653210.0.17763.0
Affected range stops below 10.0.17763.6532, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.513110.0.19043.0 ≤ v < 10.0.19044.513110.0.19043.0
Affected range stops below 10.0.19044.5131, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.513110.0.19045.0 ≤ v < 10.0.19045.513110.0.19045.0
Affected range stops below 10.0.19045.5131, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.446010.0.22621.0 ≤ v < 10.0.22621.446010.0.22621.0
Affected range stops below 10.0.22621.4460, so it looks safe — our inference, not a vendor statement
v < 10.0.22631.446010.0.22631.0 ≤ v < 10.0.22631.446010.0.22631.0
Affected range stops below 10.0.22631.4460, so it looks safe — our inference, not a vendor statement
v < 10.0.26100.231410.0.26100.0 ≤ v < 10.0.26100.231410.0.26100.0
Affected range stops below 10.0.26100.2314, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.751510.0.14393.0 ≤ v < 10.0.14393.751510.0.14393.0
Affected range stops below 10.0.14393.7515, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.653210.0.17763.0 ≤ v < 10.0.17763.653210.0.17763.0
Affected range stops below 10.0.17763.6532, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-287NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card