<?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://cve.radiocsirt.org</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, 07 Oct 2026 13:48:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-32723 — SandboxJS timers have an execution-quota bypass (cross-sandbox currentTicks race)</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-32723</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nyariv SandboxJS&lt;/p&gt;
&lt;p&gt;SandboxJS is a JavaScript sandboxing library. Prior to 0.8.35, SandboxJS timers have an execution-quota bypass. A global tick state (`currentTicks.current`) is shared between sandboxes. Timer string handlers are compiled at execution time using that global tick state rather than the scheduling sandbox&amp;#39;s tick object. In multi-tenant / concurrent sandbox scenarios, another sandbox can overwrite `currentTicks.current` between scheduling and execution, causing the timer callback to run under a different sandbox&amp;#39;s tick budget and bypass the original sandbox&amp;#39;s execution quota/watchdog. Version 0.8.35 fixes this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nyariv SandboxJS&lt;/p&gt;
&lt;p&gt;SandboxJS is a JavaScript sandboxing library. Prior to 0.8.35, SandboxJS timers have an execution-quota bypass. A global tick state (`currentTicks.current`) is shared between sandboxes. Timer string handlers are compiled at execution time using that global tick state rather than the scheduling sandbox&amp;#39;s tick object. In multi-tenant / concurrent sandbox scenarios, another sandbox can overwrite `currentTicks.current` between scheduling and execution, causing the timer callback to run under a different sandbox&amp;#39;s tick budget and bypass the original sandbox&amp;#39;s execution quota/watchdog. Version 0.8.35 fixes this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-32723</guid>
    </item>
  </channel>
</rss>
