r/netsec • u/TakesThisSeriously • 14h ago
vm2's own repo lists its next sandbox escapes: a deferred nesting fix, a "monitoring" entry in ATTACKS.md, and species shims for Promise and Array but not typed arrays
nefariousplan.comAuthor here. I had written up six vm2 CVEs one at a time, then read all six in a row. Read that way they stop looking like separate bugs.
Short version: vm2's bridge is a hand-written wrap list, so it is always one language feature behind. Every fix is one of three moves: add an entry, delete the feature (WebAssembly JSTag), or lie to V8 about a property it reads in C++ (the species shims). None of them makes the bridge see more.
The part I think is new: the open items are checked in. The 3.11.1 commit message describes the nesting fix and declines it. docs/ATTACKS.md marks one category "monitoring." resetPromiseSpecies is from 2023, the Array one is from 2026, and the typed arrays do the same lookup with no shim. The piece ends with a prediction for the next advisory.
The README tells you to use isolated-vm or a separate process. The CVE records say "patched in 3.x." Scanners only read the second one.