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

Sandbox escape / RCE in SandboxJS via unwrapped function return values

IdentifiersCVE-2026-25520CWE-74· Improper Neutralization of Special…

In SandboxJS (a JavaScript sandboxing library) versions prior to 0.8.29, the return values of functions executed in the sandbox are not wrapped with the library’s protective wrappers. This allows sandboxed code to leverage Object.values/Object.entries to obtain an Array that contains a reference to the host environment’s Function constructor. By then using Array.prototype.at to retrieve that constructor, an attacker can invoke the host Function constructor to execute arbitrary code outside of the sandbox, resulting in a full sandbox escape. The issue is fixed in SandboxJS 0.8.29.

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, enabling arbitrary code execution in the host context outside SandboxJS’s intended restrictions (i.e., compromise of confidentiality, integrity, and availability of the host process/environment running the sandboxed code).

Mitigation

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

If immediate upgrade is not possible, avoid running untrusted code with SandboxJS. Where use is unavoidable, execute SandboxJS in a strongly isolated environment (e.g., separate container/VM) with minimal privileges, restricted filesystem access, and constrained network/egress to reduce impact of a sandbox escape.

Remediation

Patch, then assume compromise.

Upgrade @nyariv/sandboxjs (SandboxJS) to version 0.8.29 or later, which includes the fix for CVE-2026-25520.
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 activity6

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