<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 11 Nov 2026 04:31:28 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-80301</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-80301</link>
      <description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This escape vector bypasses the sandbox&amp;#39;s intended process and file isolation boundaries and can be chained with other host-level privilege escalation techniques.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This escape vector bypasses the sandbox&amp;#39;s intended process and file isolation boundaries and can be chained with other host-level privilege escalation techniques.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-80301</guid>
    </item>
    <item>
      <title>GHSA-8r49-5pg7-mh6x</title>
      <link>https://db.gcve.eu/vuln/ghsa-8r49-5pg7-mh6x</link>
      <description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This escape vector bypasses the sandbox&amp;#39;s intended process and file isolation boundaries and can be chained with other host-level privilege escalation techniques.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This escape vector bypasses the sandbox&amp;#39;s intended process and file isolation boundaries and can be chained with other host-level privilege escalation techniques.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-8r49-5pg7-mh6x</guid>
    </item>
  </channel>
</rss>
