CVE-2026-92958 vm2 before 3.11.7 Denylist Bypass via fs/promises
Attackers can bypass sandbox restrictions to access filesystem APIs and execute code when specific denylist configurations are used.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-92958?
CVE-2026-92958 is a high-severity vulnerability in patriksimek vm2, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
vm2 through 3.11.6 contains a builtin-module denylist bypass in NodeVM. When the embedder uses the builtin wildcard together with negative entries (e.g. require: { builtin: ['*', '-fs', '-child_process'] }), negative entries are matched by exact module name in lib/builtin.js, so -fs removes only the builtin named fs and does not remove builtin subpaths such as fs/promises. Sandboxed code can therefore call require('fs/promises') or require('node:fs/promises') and reach the promise-based filesystem API despite fs being denied; node: prefix handling is likewise inconsistent (a -node:fs/promises entry does not block require('fs/promises')). Host file creation and writing were confirmed via fsp.writeFile(), and other fs/promises operations (cp, mkdir, rename, rm, rmdir, truncate, read operations, etc.) are also reachable. This issue is fixed in vm2 3.11.7.
Weakness: CWE-269
Which versions are affected by CVE-2026-92958?
2 open source packages ship an affected version, including vm2.
| Package | Affected | Fixed in |
|---|---|---|
vm2 npm | All versions | 3.11.7 |
vm2 npm | All versions | 3.11.7 |
How do I fix CVE-2026-92958?
Upgrade vm2 to 3.11.7 or later.
Is CVE-2026-92958 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92958 exists.
Sources
Also known as CLEANSTART-2026-YW49143, CLSA-2026-1790940570, ECHO-9eab-0368-ced7, GHSA-6rh5-qq4q-97xh, MINI-8q28-jm93-r69v, ROOT-APP-NPM-CVE-2026-92958.