<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T18:45:17.139243+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-32723</id>
    <title>fkie_cve-2026-32723</title>
    <updated>2026-09-28T18:45:17.158168+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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'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's tick budget and bypass the original sandbox's execution quota/watchdog. Version 0.8.35 fixes this issue.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-32723"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-7p5m-xrh7-769r</id>
    <title>GHSA-7p5m-xrh7-769r — SandboxJS has an execution-quota bypass (cross-sandbox currentTicks race) in SandboxJS timers</title>
    <updated>2026-09-28T18:45:17.158234+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @nyariv/sandboxjs</p>
<p>## Summary</p>
<p>Assumed repo path is `/Users/zwique/Downloads/SandboxJS-0.8.34` (no `/Users/zwique/Downloads/SandboxJS` found). 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'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's tick budget and bypass the original sandbox's execution quota/watchdog.</p>
<p>**Impact:** execution quota bypass → CPU/resource abuse</p>
<p>---</p>
<p>## Details</p>
<p>- **Affected project:** SandboxJS (owner: nyariv)
- **Assumed checked-out version:** `SandboxJS-0.8.34` at `/Users/zwique/Downloads/SandboxJS-0.8.34`</p>
<p>### Vulnerable code paths</p>
<p>- **`/src/eval.ts`** — `sandboxFunction` binds `ticks` using `ticks || currentTicks.current`:
  ```
  createFunction(..., ticks || currentTicks.current, { ...context, ... })
  ```
  Relevant lines: 44, 53, 164, 167.</p>
<p>- **`/src/evaluator.ts` / `/src/executor.ts`** — global ticks:
  ```
  export const currentTicks = { current: { ticks: BigInt(0) } as Ticks };
  ```
  and
  ```
  _execNoneRecurse(...) { currentTicks.current = ticks; ... }
  ```
  Relevant lines: ~1700, 1712.</p>
<p>- **`sandboxedSetTimeout`** compiles string handlers at execution time, not at scheduling time, which lets `currentTicks.current` be the wrong sandbox's ticks when com…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-7p5m-xrh7-769r"/>
  </entry>
</feed>
