Isolated-vm Flaw Lets Sandboxed JavaScript Escape to Host for Potential RCE
- ID
- 16090
- Status
- summarized
- Published
- 20 Aug 2026, 9:48 PM
- Fetched
- 20 Aug 2026, 11:45 PM
- Provider
- The Hacker News
- Category
- security
- Original URL
- https://thehackernews.com/2026/08/isolated-vm-flaw-lets-sandboxed.html
- Source URL
- https://feeds.feedburner.com/TheHackersNews
Summary
- Score
- 7.5
- Created
- 20 Aug 2026, 11:48 PM
- Tags
- Audience
- developersai_agent_usersai_ml_learners
What happened
A critical sandbox-escape vulnerability (GHSA-864f-rcv7-6rh4) in isolated-vm—a Node.js library with ~1M weekly npm downloads for running untrusted JavaScript in V8 Isolates—lets sandboxed code corrupt host memory via a type confusion bug in ExternalCopy's transferList handling. Researcher Cristian-Alexandru Staicu demonstrated a full guest-to-host escape starting from a single ivm.Reference. The flaw affects all versions through 7.0.0 and is patched in 6.2.0 and 7.0.1.
Why it matters
If you run isolated-vm to execute untrusted or model-generated JavaScript (common in AI agent code-execution tooling), upgrade immediately to 6.2.0 or 7.0.1—anything earlier is exploitable for host-process RCE. Audit whether your agent architecture passes ExternalCopy objects with a transferList, since that is the exact attack surface.
Discussion angle
How many AI agent frameworks that offer 'safe' JavaScript code execution actually rely on isolated-vm under the hood, and what does this escape say about trusting V8 Isolates as a security boundary for model-generated code?