CVE-2026-47209: high-severity vulnerability in patriksimek vm2
vm2: Bridge Proxy set trap ignores receiver parameter, enabling host object property injection via prototype chain
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.6epss 0.3%
vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, the BaseHandler.set trap in bridge.js (line 1231) ignores the receiver parameter and unconditionally writes to the host target object. Per the Proxy set trap specification, when receiver !== proxy (e.g., when a child object inherits from the proxy via Object.create), the property assignment should create an own property on the receiver, not on the proxy target. The current implementation always calls otherReflectSet(object, key, value) against the host target, causing all inherited property writes to leak through to the host object. This bug provides an alternative attack vector for writing dangerous cross-realm Symbol keys (e.g., nodejs.util.promisify.custom) to host objects, bypassing any future per-trap isDangerousCrossRealmSymbol guard on the direct set path. This issue has been patched in version 3.11.4.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
Affected products
patriksimek · vm2Related CVEs — patriksimek vm2
In the same product, most dangerous first.
CVE-2023-30547CRITICALSandbox Escape in vm2EPSS 73.0%CVE-2023-29017CRITICALvm2 Sandbox Escape vulnerabilityEPSS 63.2%CVE-2022-36067CRITICALvm2 vulnerable to Sandbox Escape before v3.9.11EPSS 47.9%CVE-2023-32314CRITICALSandbox EscapeEPSS 8.1%CVE-2023-37903CRITICALSandbox Escape in vm2EPSS 4.2%CVE-2023-37466CRITICALvm2 Sandbox Escape vulnerabilityEPSS 3.9%