AVAST ANTIVIRUS / ONE / PREMIUM SECURITY / ULTIMATE · CVE-2026-80301 · Other
FIX → 26.7 ✓ verified
The Avast sandbox does not block access to the Windows Task Scheduler COM interfaces, so code running inside the sandbox can schedule tasks on the host. An attacker with low privileges can use this to escape the sandbox and run code with elevated privileges outside it.
first public Nov 6, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Windows machines running Avast (Antivirus, One, Premium Security, Ultimate), AVG (Antivirus Free, Internet Security, Ultimate) or Norton (Antivirus Plus, 360 Standard/Deluxe/Advanced) below version 26.7. The attacker must already be able to run code inside the Avast sandbox, then can use Task Scheduler COM access to run code with elevated privileges. Systems on 26.7 or later, and non-Windows systems, can skip it.
Not affected if non-windows, unknown, version-26.7-or-later
Who cares avast, avg, endpoint-security, norton, sandbox-escape, windows
Improper isolation in the Avast sandbox on Windows allows a local, low-privileged attacker executing inside the sandbox to access COM interfaces to the Task Scheduler service, escape containment, and execute code with elevated privileges outside the sandbox.
The sandbox virtualizes file system and registry access but does not adequately restrict COM interface access to Task Scheduler. A process inside the sandbox can instantiate COM objects bound to Task Scheduler functionality and invoke methods to schedule and execute tasks on the host system. The Task Scheduler COM pathway is not blocked by the sandbox policy, allowing arbitrary code execution in the host security context.
This escape vector bypasses the sandbox's intended process and file isolation boundaries and can be chained with other host-level privilege escalation techniques.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
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.
Upgrade to 26.7