Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Critical severity, with a CVSS score of 9.9, published 17 September 2026.
- Which products and versions are affected?
- vm2 (npm) >= 3.11.3, <= 3.11.6; Vm2 3.11.3 to 3.11.6.
- Is there a fix for This vulnerability?
- A patch was published on 2026: Fixed in vm2 3.11.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run vm2 (npm) or Vm2 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability stems from inadequate isolation of the node:sqlite builtin module. vm2's readonly() wrapper prevents property assignment but does not restrict method calls; sandboxed code can invoke DatabaseSync.loadExtension() to load a native library from the plugin's __dirname, causing SQLite to execute the library's native entry point in the host process context. The resolver also permits double-prefixing ('node:node:sqlite') to bypass certain checks. This requires the node:sqlite builtin to be explicitly enabled or included in a wildcard allowlist.
Affected products
- vm2 3.11.3 to 3.11.6
Timeline
- 2026-08-24: disclosed
- 2026: patched: Fixed in vm2 3.11.7