- Exploited
- No known exploitation
- Fix
- Fixed in 26.7
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 26.7.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Avast sandbox on Windows can be escaped through its Task Scheduler COM interface, letting a local, low-privileged attacker already running inside the sandbox execute code on the host with elevated privileges. The sandbox does not block access to Task Scheduler COM objects, so an attacker can use them to schedule and run tasks outside the sandbox.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 26.7.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Gen Digital Avast Antivirus, Avast One, Avast Premium Security, Avast Ultimate
fixed in 26.7
- Gen Digital AVG Antivirus Free, AVG Internet Security, AVG Ultimate
fixed in 26.7
- Gen Digital Norton Antivirus Plus, Norton 360 Standard, Norton 360 Deluxe, Norton 360 Advanced
fixed in 26.7
Evidence 4
- Advisory
- Patch
- Patch
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-80301
Is CVE-2026-80301 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-80301?
Avast Antivirus, Avast One, Avast Premium Security, Avast Ultimate: before 26.7. AVG Antivirus Free, AVG Internet Security, AVG Ultimate: before 26.7. Norton Antivirus Plus, Norton 360 Standard, Norton 360 Deluxe, Norton 360 Advanced: before 26.7.Source: cve.now feed data
How do I fix CVE-2026-80301?
Upgrade to a fixed version: 26.7.Source: cve.now feed data