Threats / Microsoft / CVE-2024-49039
CVE-2024-49039
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Microsoft Windows vulnerability
Microsoft Windows Task Scheduler privilege escalation vulnerability (CWE-287) allows local applications to escape AppContainer restrictions and access privileged RPC functions, enabling unauthorized privilege elevation.
Verdict
Today item, not a backlog item.
A local privilege escalation flaw in Windows Task Scheduler permits attackers to bypass application sandboxing and gain elevated system access. Active exploitation and ransomware deployment confirm critical operational risk.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
21 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 2024-11-12), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.13719 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-287 Improper Authentication — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
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 deliver a malicious local application to a target system through social engineering or supply chain compromise.
Business
User systems face direct compromise risk from seemingly benign software installations.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the Task Scheduler flaw to escape the AppContainer sandbox that would normally restrict my application's capabilities.
Business
Containment controls fail, allowing malware to operate with fewer restrictions than intended.
3
Lateral reach — past segmentation narrative 3
Attacker
I invoke privileged RPC functions to escalate my process to system or administrator level.
Business
Attackers gain full system control, enabling data theft, lateral movement, and persistence.
4
Data at risk — exfiltration narrative 4
Attacker
I deploy ransomware or establish persistent backdoor access across the compromised environment.
Business
Operations halt due to encryption or data exfiltration; recovery costs and downtime escalate significantly.
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