Lucene search
+L

3 matches found

Github Security Blog
Github Security Blog
•added 2026/10/01 3:42 p.m.•6 views

vm2: Incomplete nodejs.* symbol filtering lets sandbox override host WebStream state checks

Summary vm2 current head v3.11.5, commit 7a1f5100b96f48d34e0fe104ab37c0acc5944f92 still exposes registered Node.js internal symbols from host WebStream prototypes to sandbox code. The prior nodejs. symbol hardening blocks Symbol.for'nodejs.' at the source, but the extraction filters and bridge...

8.9CVSS5.7AI score0.00461EPSS
SaveExploits0References6Affected Software1
Github Security Blog
Github Security Blog
•added 2026/05/29 5:44 p.m.•24 views

vm2 has a sandbox escape via unblocked cross-realm Symbol.for keys + missing bridge write-trap symbol checks

Summary vm2 3.11.2 Symbol.for override in setup-sandbox.js only intercepts 2 of 9 dangerous Node.js cross-realm symbols. Combined with the bridge's set/defineProperty/deleteProperty traps having no isDangerousCrossRealmSymbol key check, sandbox code can obtain real cross-realm symbols, write them...

8.7CVSS5.9AI score0.00442EPSS
SaveExploits0References5Affected Software1
OSV
OSV
•added 2026/05/29 5:44 p.m.•30 views

GHSA-M5Q2-4FM3-VFQP vm2 has a sandbox escape via unblocked cross-realm Symbol.for keys + missing bridge write-trap symbol checks

Summary vm2 3.11.2 Symbol.for override in setup-sandbox.js only intercepts 2 of 9 dangerous Node.js cross-realm symbols. Combined with the bridge's set/defineProperty/deleteProperty traps having no isDangerousCrossRealmSymbol key check, sandbox code can obtain real cross-realm symbols, write them...

8.7CVSS5.9AI score0.00442EPSS
SaveExploits0References5
Rows per page
Query Builder