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

SandboxJS sandbox escape via Function.caller leading to arbitrary host JavaScript execution

IdentifiersCVE-2026-43898CWE-94· Improper Control of Generation of…

CVE-2026-43898 is a critical sandbox escape vulnerability in the @nyariv/sandboxjs JavaScript sandboxing library affecting versions prior to 0.9.6 (including 0.9.5 and earlier). Sandbox-defined functions improperly expose sensitive function properties such as Function.caller, which allows sandboxed code to recover the internal host-side runtime callback LispType.Call. Because this callback can then be invoked with attacker-controlled fake context and obj/parameter values, an attacker can abuse the runtime’s trust assumptions to extract blocked host statics, recover the real host Function constructor, and escape the sandbox boundary. Once the genuine host Function constructor is obtained, the attacker can execute arbitrary JavaScript in the host environment. Supporting context indicates the vulnerable logic is in SandboxJS property access handling, specifically in prop.ts within addOps, where access to caller, callee, and arguments was not properly blocked.

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 results in a complete sandbox escape and arbitrary code execution in the host JavaScript environment. In Node.js deployments, this can lead to full remote code execution on the underlying host, including execution of system commands via built-in modules such as child_process. The impact spans confidentiality, integrity, and availability, because an attacker can access sensitive host data, modify application or system state, and disrupt service operation. The vulnerability crosses the intended isolation boundary between untrusted sandboxed code and the host runtime.

Mitigation

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

If immediate patching is not possible, do not process or execute untrusted JavaScript with affected SandboxJS versions. Reduce exposure by disabling any feature that accepts attacker-controlled scripts, isolating the service at the OS/container level, and applying strict runtime containment so that a sandbox escape does not directly yield host compromise. However, the primary effective mitigation is upgrading to 0.9.6 or later; no complete temporary workaround is documented beyond avoiding untrusted script execution.

Remediation

Patch, then assume compromise.

Upgrade @nyariv/sandboxjs to version 0.9.6 or later. Version 0.9.6 fixes the issue by blocking access to the dangerous function properties caller, callee, and arguments from sandboxed code, preventing leakage of the internal LispType.Call callback and the subsequent recovery of the host Function constructor.
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 activity9

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