vm2 before 3.12.2 does not apply its Buffer backing-store ownership invariant (byteOffset === 0 and…
Historical advisory recorded 25 Oct 2026 04:17:26 UTC. Read the latest advisory.
nvd · CVE-2026-100723
Publishedvm2 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-100723 · CVE overview and exploitation status
nvd · CVE-2026-100723
- https://github.com/patriksimek/vm2/commit/4f2508abeb252aa86eb6761c78b3b000248fb089
- https://github.com/patriksimek/vm2/commit/5214b02ef13b82497fcb917b45320dfd014ffd09
- https://github.com/patriksimek/vm2/security/advisories/GHSA-489w-w794-jq94
- https://www.vulncheck.com/advisories/vm2-before-3.12.2-memory-disclosure-via-zlib-buffer-pool
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.