Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-25520: CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') in nyariv SandboxJS

0
Critical
VulnerabilityCVE-2026-25520cvecve-2026-25520cwe-74
Published: Fri Feb 06 2026 (02/06/2026, 19:53:24 UTC)
Source: CVE Database V5
Vendor/Project: nyariv
Product: SandboxJS

Description

SandboxJS is a JavaScript sandboxing library. Prior to 0.8.29, The return values of functions aren't wrapped. Object.values/Object.entries can be used to get an Array containing the host's Function constructor, by using Array.prototype.at you can obtain the hosts Function constructor, which can be used to execute arbitrary code outside of the sandbox. This vulnerability is fixed in 0.8.29.

AI-Powered Analysis

AILast updated: 02/06/2026, 20:15:17 UTC

Technical Analysis

CVE-2026-25520 is a critical vulnerability identified in the JavaScript sandboxing library SandboxJS, specifically in versions prior to 0.8.29. SandboxJS aims to isolate JavaScript code execution to prevent malicious scripts from escaping the sandbox. However, the vulnerability stems from improper neutralization of special elements in output used by downstream components (CWE-74). The core issue is that the return values of functions executed inside the sandbox are not wrapped or sanitized properly. Attackers can exploit this by using Object.values or Object.entries to retrieve an array containing the host environment's Function constructor. Leveraging Array.prototype.at, an attacker can access this constructor and execute arbitrary JavaScript code outside the sandbox boundaries. This results in a complete bypass of the sandbox restrictions, allowing remote code execution (RCE) on the host system. The vulnerability requires no authentication or user interaction and can be exploited remotely over the network. The CVSS v3.1 base score is 10.0, reflecting the highest severity due to its impact on confidentiality, integrity, and availability, ease of exploitation, and scope of affected systems. The issue was reserved on 2026-02-02 and published on 2026-02-06. Although no known exploits are reported in the wild yet, the critical nature of this flaw demands urgent attention. The vulnerability is fixed in SandboxJS version 0.8.29, which properly wraps return values to prevent access to the host's Function constructor.

Potential Impact

For European organizations, this vulnerability poses a severe risk, especially those relying on SandboxJS for secure JavaScript execution in web applications, cloud services, or embedded systems. Exploitation can lead to full remote code execution, allowing attackers to execute arbitrary commands, steal sensitive data, manipulate application logic, or disrupt services. This could result in data breaches, service outages, and loss of trust. Organizations in sectors such as finance, healthcare, government, and critical infrastructure are particularly at risk due to the sensitive nature of their data and operations. The vulnerability's network exploitable nature means attackers can compromise systems without prior access or user interaction, increasing the likelihood of widespread impact if unpatched. Additionally, the sandbox bypass undermines any security guarantees provided by SandboxJS, potentially exposing other internal systems and networks to compromise.

Mitigation Recommendations

1. Immediately upgrade all instances of SandboxJS to version 0.8.29 or later, where the vulnerability is fixed. 2. Audit all applications and services to identify usage of SandboxJS and verify the version in use. 3. Implement runtime monitoring and anomaly detection to identify suspicious JavaScript execution patterns indicative of sandbox escapes. 4. Employ defense-in-depth by restricting network access and privileges of services using SandboxJS to limit potential damage from exploitation. 5. Review and harden Content Security Policies (CSP) to reduce the risk of malicious script injection. 6. Conduct penetration testing focused on sandbox escape techniques to validate the effectiveness of mitigations. 7. Stay informed on any emerging exploits or patches related to this vulnerability. 8. For environments where immediate patching is not feasible, consider disabling or isolating SandboxJS usage temporarily until patched.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-02T18:21:42.487Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69864849f9fa50a62f2e0353

Added to database: 2/6/2026, 8:00:09 PM

Last enriched: 2/6/2026, 8:15:17 PM

Last updated: 2/6/2026, 9:06:54 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats