SandboxJS Sandbox Escape via Unprotected AsyncFunction Constructor (CVE-2026-23830)
CVE-2026-23830 is a maximum-severity (CVSS 10.0) sandbox-escape vulnerability in SandboxJS, a library intended to safely execute untrusted JavaScript. The issue allows attackers to break out of the sandbox and achieve arbitrary code execution on the host by leveraging gaps in SandboxJS’s “safe replacement” model for dangerous constructors.
The flaw stems from SandboxJS mapping the global Function constructor to a sandboxed equivalent, but (in affected versions) failing to similarly isolate the “Async” and generator constructor families: AsyncFunction, GeneratorFunction, and AsyncGeneratorFunction. Although these constructors are not directly exposed as globals, they can be obtained via an instance’s .constructor (e.g., (async () => {}).constructor); because the executor returns the native host AsyncFunction when it is not present in the safe-replacement map, an attacker can create new functions that execute in the global scope and bypass sandbox restrictions. SandboxJS 0.8.26 is reported as the patched version.
Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
2 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-23830 disclosure details SandboxJS sandbox escape
Public disclosure described CVE-2026-23830 as a maximum-severity flaw in SandboxJS caused by missing protections for asynchronous and generator function constructors. Attackers could access the native host AsyncFunction via the .constructor property and escape the sandbox to gain full host access.
SandboxJS releases version 0.8.26 to fix CVE-2026-23830
SandboxJS fixed a critical sandbox escape vulnerability in version 0.8.26 by properly isolating AsyncFunction, GeneratorFunction, and AsyncGeneratorFunction within its sandboxing mechanism. The flaw affected all versions prior to 0.8.26 and could allow arbitrary code execution outside the sandbox.
Sources
2 references tracked. Mallory keeps watching after this page renders.
See the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Related stories
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Critical SandboxJS Sandbox-Escape Vulnerabilities Enabling Host Code Execution
Multiple **critical vulnerabilities in *SandboxJS***—a JavaScript sandboxing library used to run untrusted code—were disclosed as enabling **sandbox escape and arbitrary code execution on the host**, with several issues scored **CVSS 10.0**. Reported flaws include **CVE-2026-25520**, **CVE-2026-25586**, **CVE-2026-25587**, and **CVE-2026-25641**, described as providing multiple paths to break out of SandboxJS’s isolation guarantees and take over the underlying runtime environment. Technical details published for **CVE-2026-25520** indicate that, prior to *SandboxJS* `0.8.29`, **function return values are not wrapped**, allowing attackers to use `Object.values()`/`Object.entries()` to obtain an array containing the host’s `Function` constructor (e.g., via `Array.prototype.at`), which can then be used to execute code outside the sandbox; the issue is fixed in `0.8.29` (with a referenced upstream commit and GitHub Security Advisory). Additional reported escape vectors include manipulation of supposedly safe prototypes (e.g., overwriting `Map.prototype.has` via a bug in the library’s `let` implementation) and a **host prototype pollution** condition tied to unsafe property-checking logic, collectively undermining the library’s core containment model.
Mar 21, 2026
Critical SandboxJS Sandbox Escape Enables Host Remote Code Execution
A critical vulnerability in the npm package **`@nyariv/sandboxjs`** allows attackers to escape the JavaScript sandbox and execute arbitrary code on the host system. The issue, tracked as **`CVE-2026-43898`**, affects all versions through **`0.9.5`** and has been rated **CVSS 10.0**. Public reporting and GitHub advisory coverage describe the flaw as a sandbox escape that can be triggered without credentials or user interaction, creating a path to full host takeover when applications use the library to process untrusted JavaScript. The bug stems from improper exposure of internal callback functionality during function property access, including **`caller`**, **`callee`**, and **`arguments`**, enabling attackers to recover the host **`Function`** constructor and run arbitrary JavaScript or system commands. Separate advisory reporting also describes a sandbox escape caused by a **TOCTOU** bug in key handling during property access, underscoring broader weaknesses in the package's isolation model. Maintainers released **`0.9.6`** to block access to the dangerous properties, and organizations using SandboxJS are being urged to upgrade immediately or stop executing untrusted code with the library.
May 25, 2026
SandboxJS Sandbox Escape via Host Prototype Pollution (CVE-2026-25881)
**CVE-2026-25881** is a critical sandbox-escape flaw in *SandboxJS* (`@nyariv/sandboxjs`) that allows sandboxed JavaScript to **mutate host built-in prototypes** (e.g., `Map.prototype`, `Set.prototype`) and cause persistent **host-side prototype pollution**. The issue stems from SandboxJS’s `isGlobal` protection mechanism: when a global prototype reference is placed into an **array literal** and then retrieved, the `isGlobal` “taint” is stripped, enabling direct prototype mutation from within the sandbox. The vulnerability affects versions **prior to 0.8.31** and is fixed in **0.8.31**; CVSS v3.1 is reported as `AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H` and the weakness is mapped to **CWE-1321**. Public reporting indicates a working **proof-of-concept (PoC)** is available demonstrating multiple exploitation scenarios, including adding attacker-controlled properties to host prototypes and overwriting built-in functions. While the sandbox escape itself is the core impact, **remote code execution is application-dependent**: if the host application later uses polluted properties in sensitive sinks (example gadget: `execSync(obj.cmd)`), an attacker can potentially execute system commands (e.g., `id`). Organizations using SandboxJS to run untrusted code should prioritize upgrading to **0.8.31** and review host code paths for dangerous use of object properties that could be influenced via prototype pollution.
Mar 21, 2026