WINDOWS TASK SCHEDULER · CVE-2026-96053 · Infrastructure
NO FIX YET
Windows Task Scheduler does not neutralize special characters in a command, so an authorized local attacker can inject commands. The attacker gains higher privileges on the same machine.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Affects Windows machines where a local user with an existing account can reach Task Scheduler. The sources do not name affected Windows builds or the exact trigger, so unknown. Machines with no untrusted local users carry lower practical risk.
Who cares task-scheduler, windows
Unknown from the sources. In the analyst’s queue.
No fix yet, per the sources.
Improper neutralization of special elements used in a command ('command injection') in Windows Task Scheduler allows an authorized attacker to elevate privileges locally.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.