CVE-2026-80301 (GCVE-0-2026-80301)

Vulnerability from cvelistv5 – Published: 2026-11-06 16:01 – Updated: 2026-11-06 16:01
VLAI
Title
Avast sandbox escape via unpreserved COM pathway through Task Scheduler
Summary
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.
Severity
No CVSS data available.
CWE
  • CWE-280 - Improper Handling of Insufficient Permissions or Privileges
  • CWE-653 - Improper Isolation or Compartmentalization
Assigner
GEN CNA under the mitre root
CNA scorecard B 75/100 over 24 records in the last 180 days details
References
Impacted products
Credits
Teng Zheng Wang by VulnGuard Labs
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "affected",
          "platforms": [
            "Windows"
          ],
          "product": "Avast Antivirus, Avast One, Avast Premium Security, Avast Ultimate",
          "vendor": "Gen Digital",
          "versions": [
            {
              "lessThan": "26.7",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "platforms": [
            "Windows"
          ],
          "product": "AVG Antivirus Free, AVG Internet Security, AVG Ultimate",
          "vendor": "Gen Digital",
          "versions": [
            {
              "lessThan": "26.7",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "platforms": [
            "Windows"
          ],
          "product": "Norton Antivirus Plus, Norton 360 Standard, Norton 360 Deluxe, Norton 360 Advanced",
          "vendor": "Gen Digital",
          "versions": [
            {
              "lessThan": "26.7",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Teng Zheng Wang by VulnGuard Labs"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eImproper 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.\u003c/p\u003e\u003cp\u003eThe 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.\u003c/p\u003e\u003cp\u003eThis escape vector bypasses the sandbox\u0027s intended process and file isolation boundaries and can be chained with other host-level privilege escalation techniques.\u003c/p\u003e"
            }
          ],
          "value": "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.\n\n\n\nThe 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.\n\n\n\nThis escape vector bypasses the sandbox\u0027s intended process and file isolation boundaries and can be chained with other host-level privilege escalation techniques."
        }
      ],
      "impacts": [
        {
          "descriptions": [
            {
              "lang": "en",
              "value": "A local, low-privileged attacker executing in the Avast sandbox can access COM interfaces to Task Scheduler, execute code outside sandbox containment, and potentially achieve privilege escalation."
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-280",
              "description": "CWE-280: Improper Handling of Insufficient Permissions or Privileges",
              "lang": "en",
              "type": "CWE"
            },
            {
              "cweId": "CWE-653",
              "description": "CWE-653: Improper Isolation or Compartmentalization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-06T16:01:42.131Z",
        "orgId": "dbd8429d-f261-4b1e-94cc-ae3132817e2e",
        "shortName": "GEN"
      },
      "references": [
        {
          "name": "Gen Digital Security Advisories",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://www.gendigital.com/us/en/contact-us/security-advisories/"
        },
        {
          "name": "Avast: how to update Avast Antivirus or Avast One",
          "tags": [
            "patch"
          ],
          "url": "https://support.avast.com/en-us/article/Update-Antivirus"
        },
        {
          "name": "AVG: updating AVG AntiVirus",
          "tags": [
            "patch"
          ],
          "url": "https://support.avg.com/SupportArticleView?l=en\u0026urlname=Update-AVG-Antivirus"
        },
        {
          "name": "Norton: keep your Norton device security up to date",
          "tags": [
            "patch"
          ],
          "url": "https://support.norton.com/sp/en/us/home/current/solutions/v20240108175512167"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eGen Digital has released a fix in Avast, AVG, and Norton version \u003cstrong\u003e26.7 and later\u003c/strong\u003e. The fix restricts COM interface access to Task Scheduler from within the sandbox by adding sandbox policy rules that block the COM pathway.\u003c/p\u003e\u003cp\u003eUpgrade to version \u003cstrong\u003e26.7 or later\u003c/strong\u003e to remediate this issue.\u003c/p\u003e"
            }
          ],
          "value": "Gen Digital has released a fix in Avast, AVG, and Norton version 26.7 and later. The fix restricts COM interface access to Task Scheduler from within the sandbox by adding sandbox policy rules that block the COM pathway.\n\n\n\nUpgrade to version 26.7 or later to remediate this issue."
        }
      ],
      "source": {
        "discovery": "EXTERNAL"
      },
      "title": "Avast sandbox escape via unpreserved COM pathway through Task Scheduler",
      "x_generator": {
        "engine": "Vulnogram 1.0.5"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "dbd8429d-f261-4b1e-94cc-ae3132817e2e",
    "assignerShortName": "GEN",
    "cveId": "CVE-2026-80301",
    "datePublished": "2026-11-06T16:01:42.131Z",
    "dateReserved": "2026-08-26T08:11:54.260Z",
    "dateUpdated": "2026-11-06T16:01:42.131Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-80301",
      "date": "2026-11-07",
      "epss": "0.0016",
      "percentile": "0.05245"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "affected",
                "platforms": [
                  "Windows"
                ],
                "product": "Avast Antivirus, Avast One, Avast Premium Security, Avast Ultimate",
                "vendor": "Gen Digital",
                "versions": [
                  {
                    "lessThan": "26.7",
                    "status": "affected",
                    "version": "0",
                    "versionType": "custom"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "platforms": [
                  "Windows"
                ],
                "product": "AVG Antivirus Free, AVG Internet Security, AVG Ultimate",
                "vendor": "Gen Digital",
                "versions": [
                  {
                    "lessThan": "26.7",
                    "status": "affected",
                    "version": "0",
                    "versionType": "custom"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "platforms": [
                  "Windows"
                ],
                "product": "Norton Antivirus Plus, Norton 360 Standard, Norton 360 Deluxe, Norton 360 Advanced",
                "vendor": "Gen Digital",
                "versions": [
                  {
                    "lessThan": "26.7",
                    "status": "affected",
                    "version": "0",
                    "versionType": "custom"
                  }
                ]
              }
            ],
            "source": "security@nortonlifelock.com"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "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.\n\n\n\nThe 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.\n\n\n\nThis escape vector bypasses the sandbox\u0027s intended process and file isolation boundaries and can be chained with other host-level privilege escalation techniques."
          }
        ],
        "id": "CVE-2026-80301",
        "lastModified": "2026-11-06T16:18:58.870",
        "metrics": {},
        "published": "2026-11-06T16:18:58.870",
        "references": [
          {
            "source": "security@nortonlifelock.com",
            "url": "https://support.avast.com/en-us/article/Update-Antivirus"
          },
          {
            "source": "security@nortonlifelock.com",
            "url": "https://support.avg.com/SupportArticleView?l=en\u0026urlname=Update-AVG-Antivirus"
          },
          {
            "source": "security@nortonlifelock.com",
            "url": "https://support.norton.com/sp/en/us/home/current/solutions/v20240108175512167"
          },
          {
            "source": "security@nortonlifelock.com",
            "url": "https://www.gendigital.com/us/en/contact-us/security-advisories/"
          }
        ],
        "sourceIdentifier": "security@nortonlifelock.com",
        "vulnStatus": "Received",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-280"
              },
              {
                "lang": "en",
                "value": "CWE-653"
              }
            ],
            "source": "security@nortonlifelock.com",
            "type": "Secondary"
          }
        ]
      }
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.