CVE-2026-25586
Nyariv Sandboxjs ≤ 0.8.29
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2026-25586 is a critical-severity Injection (CWE-74) vulnerability in Nyariv Sandboxjs. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 47th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25586 is a critical sandbox escape vulnerability in SandboxJS, an open-source JavaScript sandboxing library. Versions prior to 0.8.29 are affected, where an attacker can shadow the hasOwnProperty method on a sandbox object. This action disables prototype whitelist enforcement during property access, allowing direct access to blocked prototype properties such as __proto__. Consequently, this enables host Object.prototype pollution and persistent impact across multiple sandboxes. The vulnerability carries a CVSS v3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) and is associated with CWE-74.
Remote attackers can exploit this vulnerability over the network with low complexity, requiring no privileges, authentication, or user interaction. By executing malicious JavaScript code within a sandboxed environment, they can bypass isolation controls, pollute the host Object.prototype, and achieve persistent effects that propagate across sandboxes. This grants high-impact confidentiality, integrity, and availability compromises with a changed scope, potentially leading to full code execution on the host environment.
The vulnerability was fixed in SandboxJS version 0.8.29, as detailed in the project's GitHub security advisory (GHSA-jjpw-65fv-8g48) and the corresponding commit (67cb186c41c78c51464f70405504e8ef0a6e43c3). Security practitioners should update to 0.8.29 or later and review deployments using SandboxJS for exposure, particularly in web applications or Node.js environments relying on sandboxing for untrusted code execution.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-5592
Vulnerability Data
SandboxJS is a JavaScript sandboxing library. Prior to 0.8.29, a sandbox escape is possible by shadowing hasOwnProperty on a sandbox object, which disables prototype whitelist enforcement in the property-access path. This permits direct access to __proto__ and other blocked prototype…
more
properties, enabling host Object.prototype pollution and persistent cross-sandbox impact. This vulnerability is fixed in 0.8.29.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.1V1.2.3V1.2.5V1.2.8
Mitigating Controls (NIST 800-53 r5) AI
SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and output encoding that prevent injection flaws.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches injection vulnerabilities before release.
Logging supports detection of injection attempts but does not prevent the weakness.
Monitoring activities can identify active injection attacks after they occur.
Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.
Application security requirements explicitly call for controls against injection attacks in software design.
Secure architecture principles reduce injection surfaces but do not prescribe specific neutralization techniques.