CVE-2026-92958
- Source
- https://cve.org/CVERecord?id=CVE-2026-92958
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-92958.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-92958
- Aliases
-
- GHSA-6rh5-qq4q-97xh
- Published
- 2026-09-17T13:46:15Z
- Modified
- 2026-09-18T03:48:43Z
- Severity
-
- 8.4 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:H/SA:L CVSS Calculator
- Summary
- vm2 before 3.11.7 Denylist Bypass via fs/promises
- Details
-
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.
- Database specific
{ "cna_assigner": "VulnCheck", "cwe_ids": [ "CWE-269" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/92xxx/CVE-2026-92958.json" }- References