Security readout for executives and security teams
Plain-English summary
SandboxJS versions before 0.8.26 can let code escape the intended JavaScript sandbox and run with access to the host environment. If your application uses SandboxJS to run untrusted or customer-supplied JavaScript, this is a high-urgency issue because the stated impact is remote code execution.
Executive priority
Treat as urgent for any service that runs external or tenant-provided JavaScript through SandboxJS. The business risk is host compromise from a failed sandbox boundary. Prioritize patching internet-facing or multi-tenant systems first.
Technical view
The advisory states SandboxJS failed to isolate AsyncFunction, GeneratorFunction, and AsyncGeneratorFunction constructors. Accessing a function instance constructor could return the native host constructor rather than the sandboxed replacement, allowing newly created functions to execute outside the sandbox. The issue is fixed in version 0.8.26.
Likely exposure
Exposure is most likely in Node.js or JavaScript applications that depend on nyariv/SandboxJS before 0.8.26 and execute untrusted, semi-trusted, or user-controlled scripts. Applications using SandboxJS only for trusted internal code have lower practical exposure, but should still update.
Exploitation context
The CVE record assigns CVSS 10.0 with network attack vector, low complexity, no privileges, and no user interaction. The provided sources do not state active exploitation, and it is not marked KEV in the source bundle.
Researcher notes
The issue centers on constructor access returning native host function constructors not present in the safe replacement map. Avoid assuming exploitability in products without confirming SandboxJS use and untrusted code execution paths. Public sources name 0.8.26 as the patched version.
Mitigation direction
- Upgrade SandboxJS to version 0.8.26 or later.
- Identify direct and transitive uses of nyariv/SandboxJS in application dependency manifests.
- Restrict or disable untrusted JavaScript execution until patched where feasible.
- Review vendor advisory and patch commit for implementation details.
Validation and detection
- Confirm deployed SandboxJS versions are 0.8.26 or later.
- Check lockfiles and container images for older SandboxJS packages.
- Verify applications using SandboxJS cannot execute untrusted scripts on vulnerable versions.
- Document any compensating controls if immediate upgrade is not possible.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-693: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-913: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-23830 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/nyariv/SandboxJS/security/advisories/GHSA-wxhw-j4hc-fmq6CVE reference · x_refsource_CONFIRM
- https://github.com/nyariv/SandboxJS/commit/345aee6566e47979dee5c337b925b141e7f78ccdCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.