# CVE-2026-32723: SandboxJS timers have an execution-quota bypass (cross-sandbox currentTicks race)

> Attackers can bypass execution quotas in SandboxJS by exploiting a race condition in shared timer state, allowing resource exhaustion or quota evasion.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** GHSA-7p5m-xrh7-769r

## What is CVE-2026-32723?

CVE-2026-32723 is a medium-severity vulnerability in nyariv SandboxJS, published on 18 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-32723?

2 open source packages ship an affected version, including @nyariv/sandboxjs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@nyariv/sandboxjs` | npm | All versions | 0.8.35 |
| `@nyariv/sandboxjs` | npm | All versions | 0.8.35 |

Products: Nyariv Sandboxjs.

## How do I fix CVE-2026-32723?

Upgrade @nyariv/sandboxjs to 0.8.35 or later.

## Is CVE-2026-32723 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32723 exists.

## Other vulnerabilities in nyariv SandboxJS

- [CVE-2026-43898](https://insights.sbomify.com/CVE-2026-43898/): SandboxJS: Sandbox escape via Function.caller leakage of internal call op (critical 10.0)
- [CVE-2026-34208](https://insights.sbomify.com/CVE-2026-34208/): SandboxJS: Sandbox integrity escape (critical 10.0)
- [CVE-2026-26954](https://insights.sbomify.com/CVE-2026-26954/): SandboxJS has a Sandbox Escape (critical 10.0)
- [CVE-2026-25520](https://insights.sbomify.com/CVE-2026-25520/): SandboxJS has a Sandbox Escape (critical 10.0)
- [CVE-2026-25586](https://insights.sbomify.com/CVE-2026-25586/): SandboxJS has a Sandbox Escape via Prototype Whitelist Bypass and Host Prototype Pollution (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32723 and fix it if it is affected.

What it is: CVE-2026-32723 is a medium-severity vulnerability in nyariv SandboxJS, published on 18 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32723 exists.

Affected packages and fixed versions:
- @nyariv/sandboxjs (npm): affected all versions; fixed in 0.8.35
- @nyariv/sandboxjs (npm): affected all versions; fixed in 0.8.35

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32723/ (Markdown: https://insights.sbomify.com/CVE-2026-32723/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32723
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32723
- OSV: https://osv.dev/vulnerability/CVE-2026-32723

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32723/
Summaries are generated and may contain mistakes; the official description above is the record.