CVE-2026-23830
CRITICALDescription
SandboxJS is a JavaScript sandboxing library. Versions prior to 0.8.26 have a sandbox escape vulnerability due to `AsyncFunction` not being isolated in `SandboxFunction`. 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, before version 0.8.26, 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). Version 0.8.26 patches this vulnerability.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Exploit Intelligence
Moderate risk: more likely to be exploited than 63% of all known CVEs.
References
Related Vulnerabilities
Other CWE-94 (Code Injection) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-9841 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2015-1635 | Critical | 9.8 | 100% | KEV | - |
| CVE-2025-3248 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2022-22954 | Critical | 9.8 | 100% | KEV + Ransom | - |
| CVE-2021-22204 | Medium | 6.8 | 100% | KEV | Fix |
| CVE-2012-0158 | High | 8.8 | 100% | KEV | - |
Common questions
How do I fix CVE-2026-23830?
Upgrade sandboxjs to 0.8.26 or later.
Is CVE-2026-23830 being actively exploited?
Not that we know of. CVE-2026-23830 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 1.1% is the estimated probability that it will be exploited in the next 30 days. That is higher than 63% of all scored CVEs.
How severe is CVE-2026-23830?
CVE-2026-23830 has a CVSS v3 base score of 10.0, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-23830 affect?
Published advisories record a fix for sandboxjs (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-23830
Markdown
[](https://tridentstack.com/cve/CVE-2026-23830)HTML
<a href="https://tridentstack.com/cve/CVE-2026-23830"><img src="https://tridentstack.com/cve/badge/CVE-2026-23830.svg" alt="CVE-2026-23830"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-02-12.