Topic

JavaScript sandboxing

Techniques for running untrusted JavaScript with restricted access to the host, using separate engines, fresh contexts, worker threads or process isolation.

Current clusters

security2 publishers

A sandbox escape with no CVE: isolated-vm patches, and a million weekly installs have to move

A type confusion in isolated-vm's ExternalCopy turns a single ivm.Reference into host control-flow hijack. Fixes shipped in 6.2.0 and 7.0.1, under a GHSA number and no CVE.

Publishers:securityweek.comthehackernews.com

Reality

Evidence72
Adoption62
Hype gap+12
Incentives: Insufficient
Confidence74

build2 publishers

A double-read in isolated-vm turns customer JavaScript into host code execution

GHSA-864f-rcv7-6rh4 lets guest code hand the C++ bindings one type on the first read and a different one on the second. Fixes are in 7.0.1 and 6.2.0.

Publishers:dev.toendorlabs.com

Reality

Evidence60
Adoption50
Hype gap+20
Incentives60
Confidence58

build1 publisher

Vercel puts agent-written TypeScript in QuickJS and makes host functions the real boundary

The Run SDK swaps eval's ambient authority for a worker-thread sandbox with narrow host functions and resumable interrupts. The replay semantics are the part to read twice.

Publishers:blog.vercel.com

Reality

Evidence45
Adoption22
Hype gap+18
Incentives78
Confidence50