Medium Logic error exploit reference

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

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.

Published Mar 18, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.1% (30-day exploitation probability)+0
Technical severity (medium)+3
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.12%

ahead of 2% of scored CVEs · Oct 14, 2026

Affects

Nyariv

Sandboxjs

CVSS base

4.7

Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Nyariv Sandboxjs).
Apply the fixed version or the patch documented under Remediation.
Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Nyariv	Sandboxjs	< 0.8.35	Vulnerable	NIST National Vulnerability Database
Nyariv	Sandboxjs	version < 0.8.35	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

High

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
4.8	CVSS 4.0	Medium	—	—	security-advisories@github.com via NIST National Vulnerability Database
4.8	CVSS 4.0	Medium	—	—	GitHub_M via CVE Program (cve.org) e CISA ADP
4.7	CVSS 3.1	Medium	1.0	3.6	nvd@nist.gov via NIST National Vulnerability Database

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-362 · Race Condition

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.12%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.

endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · nyariv/sandboxjs
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 4.7
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Mar 18, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

github.com/nyariv/SandboxJS/security/advisories/GHSA-7p5m-xrh7-769r
Exploit, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
github.com/nyariv/SandboxJS/commit/cc8f20b4928afed5478d5ad3d1737ef2dcfaac29
Patch, x_refsource_MISC, NIST National Vulnerability Database

Elsewhere on this site

Nyariv
every CVE for this vendor

Logic error
same class

CWE-362
other pages naming this weakness

Related CVEs (same products)

Critical CVE-2026-43898 SandboxJS: Sandbox escape via Function.caller leakage of internal call op May 28, 2026
Critical CVE-2026-34208 SandboxJS: Sandbox integrity escape Apr 6, 2026
High CVE-2026-34211 SandboxJS: Stack overflow DoS via deeply nested expressions in recursive descent parser Apr 6, 2026
High CVE-2026-34217 SandboxJS has a Sandbox Escape via Prop Object Leak in New Handler Apr 6, 2026
Critical CVE-2026-26954 SandboxJS has a Sandbox Escape Mar 13, 2026
Critical CVE-2026-25881 @nyariv/sandboxjs has host prototype pollution from sandbox via array intermediary (sandbox escape) Feb 9, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-32723 is "SandboxJS timers have an execution-quota bypass (cross-sandbox currentTicks race)", rated Medium. It affects Sandboxjs (Nyariv); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.7 describes technical severity. EPSS 0.12% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.