Description
vm2 before 3.12.2 does not apply its Buffer backing-store ownership invariant (byteOffset === 0 and buffer.byteLength === length) to Buffers returned from host builtin modules. When an application explicitly exposes Node's zlib module through NodeVM's builtin allowlist (require: { builtin: ['zlib'] }), zlib.deflateSync can return a Buffer backed by Node's shared small-buffer pool whose .buffer is the entire pool. Untrusted guest code can construct a full-width view of that ArrayBuffer (Buffer.from(result.buffer, 0, result.buffer.byteLength)) to read and modify bytes belonging to unrelated host buffers, disclosing and corrupting host-realm memory across the sandbox boundary.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| patriksimek | vm2 | < 3.12.2 | 3.12.2 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| npm | vm2 | < 3.12.2 | 3.12.2 | GHSA-489w-w794-jq94 |
Advisories 1
- WID-SEC-2026-3594 vm2: Mehrere Schwachstellen BSI CERT-Bund (WID) · Sep 27, 2026
References
- GitHub Security Advisory (GHSA-489w-w794-jq94) vendor-advisory
- Patch Commit patch
- Patch Commit patch
- VulnCheck Advisory: vm2 before 3.12.2 Memory Disclosure via zlib Buffer Pool third-party-advisory