Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
CriticalPublic exploit

Sandbox escape via callable constructor path in SandboxJS

IdentifiersCVE-2026-34208CWE-693· Protection Mechanism Failure

CVE-2026-34208 affects SandboxJS, a JavaScript sandboxing library, in versions prior to 0.8.36. SandboxJS is intended to prevent direct assignment to host global objects such as Math.random, but that protection can be bypassed through an exposed callable constructor path using this.constructor.call(target, attackerObject). In the vulnerable condition, this.constructor resolves to the internal SandboxGlobal function, and because Function.prototype.call remains permitted, attacker-controlled code can invoke that path to assign arbitrary properties onto host global objects. Those unauthorized mutations are not confined to a single sandbox execution and can persist across sandbox instances within the same process, breaking sandbox isolation guarantees.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows untrusted sandboxed code to bypass SandboxJS global-object assignment restrictions and modify host global objects. This compromises the integrity of the host execution environment and can affect confidentiality and availability depending on what globals are altered. Because the changes persist across sandbox instances in the same process, one malicious execution can taint subsequent sandbox sessions, enabling cross-session contamination, policy bypass, and broader compromise of applications relying on SandboxJS for isolation. The provided CVSS vector indicates high confidentiality and integrity impact with low availability impact and changed scope.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, do not execute untrusted code with vulnerable SandboxJS versions. Reduce exposure by isolating sandbox executions in separate processes or short-lived workers so host global mutations cannot persist across tenants or sessions in the same process. Where feasible, harden or freeze critical global objects and monitor for unexpected mutation of host globals. These are compensating controls only; the definitive fix is upgrading to 0.8.36 or later.

Remediation

Patch, then assume compromise.

Upgrade SandboxJS to version 0.8.36 or later, which fixes the exposed callable constructor path that allowed writes to host global objects. Replace vulnerable versions prior to 0.8.36 in all deployments, including transitive dependencies and embedded copies. After upgrading, restart affected processes to clear any malicious mutations that may already have been written into host global objects by prior exploitation.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
NyarivSandboxjsapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity11

Community discussion across Reddit, Mastodon, and other social sources.